Operating ProcedureExecution layer

Bolna Client Sub-Account Provisioning (Onboarding)

A checklist with 7 steps: Create the client sub-account in the Bolna workspace.

By InnovaAI ResearchPublished

What are the steps?

checklist

Bolna Client Sub-Account Provisioning (Onboarding)

  1. 01

    Create the client sub-account in the Bolna workspace

    Open the Bolna dashboard, add a sub-account named after the client, and keep each client's agents, call logs, and credits isolated so per-minute usage can be billed back cleanly.

  2. 02

    Connect the telephony provider for that sub-account

    Attach the client's Twilio or Plivo credentials inside the sub-account rather than the parent workspace, so inbound numbers and outbound caller IDs belong to the client and survive offboarding.

  3. 03

    Build the first agent in the no-code playground

    Pick the target language from the 10+ Indian language set (Hindi, Tamil, Telugu, Hinglish and others), draft the greeting and intent flow, then set custom variables for client-specific data such as order IDs or appointment slots.

  4. 04

    Wire the API authentication and tool calls

    Configure API keys for any Zapier, Make.com, or n8n webhook the agent must hit mid-call, and confirm the agent can query client data and trigger workflows before any live traffic.

  5. 05

    Run pilot calls and tune the conversation flow

    Place test inbound and outbound calls against the sub-account, check fallback-to-human escalation logic, and adjust prompts until the agent handles the top intents without dead air.

  6. 06

    Set the credit top-up and concurrency guardrails

    Decide whether the client sits on pay-as-you-go at $0.06 per minute or a committed volume plan, enable low-balance top-up alerts, and cap concurrency so a spike cannot burn the retainer margin.

  7. 07

    Hand the client a call review cadence

    Schedule a weekly review of transcripts and call outcomes from the sub-account, and document who on the agency side owns prompt changes versus who owns the client's escalation queue.