05 Use case

Multi-Entity Rollout

One account and one voice AI agent shared by every club, practice, agency or brand of a network, each entity keeping its own information. A new entity goes live in minutes.

01 In short

What is multi-entity voice AI?

Multi-entity voice AI means one CallShift account, one invoice and one voice AI agent, designed once and shared by every entity of a network: a club, a practice, an agency, a brand or a client. Each entity keeps its own information: name, address, opening hours, phone numbers and local offers.

It is built for the head office that runs several entities from a single account: franchise networks, groups of practices, multi-brand groups and BPOs that handle several clients.

How it fits togetherSchematic

Head office

  • One account
  • One invoice

Voice AI agent

Designed once, shared by every entity

Improved here, better everywhere

  • Sports clubIts own lines
  • Dental practiceIts own lines
  • Real estate agencyIts own lines
  • BrandIts own lines
  • ClientIts own lines

Each entity keeps its own information

  • Name
  • Address
  • Opening hours
  • Phone numbers
  • Local offers
One account and one invoice at head office, one shared agent, and the entities underneath, each with its own information and its own lines.
  • 1account, one invoice and one shared agent for the whole network
  • Minutesfor a new entity to go live, with no redeployment of the agent
  • 0changes to your existing setup until the first entity is created

Updated 8 October 2026

02 Who it is for

Head offices that run several entities from one account.

The reader is the head of the network, or the head of operations or customer relations at head office. An entity is one unit of the network.

NetworkAn entity is
Franchise networksA sports club, a real estate agency or a driving school
Multi-site groupsA medical, dental or accounting practice
Multi-brand groupsA brand
BPOsA client
03 What you get

Four promises for the whole network.

  1. One account, one invoice. The whole network runs from a single CallShift account and is billed on a single invoice.
  2. One agent, shared. A voice AI agent designed once and shared by every entity. Each one keeps its own information: name, address, opening hours, phone numbers and local offers.
  3. Improved once, better everywhere. An improvement validated at head office benefits every entity immediately, with no redeployment.
  4. Every line stays in its entity. A phone line cannot be tied by mistake to the agent of another entity, for inbound or outbound calls.
04 Steering

See every entity, and the network as a whole.

What head office seesSchematic

Filter by entity

  • Call logsClub A
  • ReportsClub A
  • ConsumptionClub A

Consolidated view

  • Club A
  • Club B
  • Club C

Compare entities with each other

Entities page

AgentsLinesWebhooks
Club A
Club B
Club C
No entityStill to be attached

Access rightsDifferentiated for each team

  • Quality control
  • Billing
  • Administration
What head office sees: a filter by entity, a comparison across the network, the Entities page with what is still to be attached, and the access rights of each team.
  • Call logs, reports and consumption can be filtered by entity.
  • A consolidated view of the network lets you compare entities with each other.
  • An Entities page shows, for each entity, its agents, its lines and its webhooks. The No entity filter shows what is still to be attached.
  • Differentiated access rights for your teams: quality control, billing, administration.
05 Rollout

A new entity goes live in minutes.

Adding an entitySchematic
  1. Create the entity

    Club C

    In the dashboard or through the API.

  2. Attach what exists

    Club C

    • Agents
    • Lines
    • Webhooks

    One click from the dashboard lists.

  3. Live in minutes

    Club C

    • Agents
    • Lines
    • Webhooks

    Operational

    With its own name, hours and offers.

Shared voice AI agentNo redeployment

Three steps to add an entity: create it, attach what exists, and it is live. The shared agent stays as it is.
  • A new entity is operational in minutes, with no redeployment of the agent.
  • What already exists is attached in one click from the dashboard lists.
  • The feature is optional: as long as no entity is created, nothing changes and your existing setup keeps working.
06 Line security

A line never ends up with another entity's agent.

Which line reaches which agentSchematic

Which agent can a line reach?

Line of club A

  • Agent of club ASame entityAllowed
  • Agent shared by the networkShared agentAllowed
  • Agent of club BAnother entityRefused

Checked wherever a line is associated

  • Inbound answering (telephony settings)
  • Outbound call campaigns
  • Dashboard and API

And again at the moment of each outbound call

Post-call data goes to the same entity only

Call of club A

  • Webhook of club AAllowed
  • Webhook of club BRefused
A line of club A reaches the agents of club A and the shared agents, never those of club B. Post-call data follows the same rule.
  • A line attached to an entity only works with the agents of that entity or the agents shared across the network. A club's line cannot be tied by mistake to another club's agent.
  • The check applies wherever a line is associated: answering inbound calls (telephony settings), outbound call campaigns, the dashboard and the API.
  • It is checked again at the moment of each outbound call.
  • On outbound, each call leaves from a line of the entity it is placed for. The network knows which entity calls whom, which helps comply with GDPR and the EU AI Act and clarifies responsibilities.
  • Post-call data only goes to the destinations (webhooks) of the same entity.
07 Integration

Entities are managed by API.

Entity by entitySchematic

CRM or middleware

The network's own tools

CallShift API

Filter by entity

  • Club A

    • Agents
    • Lines
    • Webhooks
    • SIP trunks
  • Club B

    • Agents
    • Lines
    • Webhooks
    • SIP trunks

SIP trunk dedicated to one location

Lines of club AEntity: club A

It takes the entity of its lines, automatically.

The network's CRM or middleware queries the CallShift API, which answers entity by entity.
  • Entities are created and managed through the API, and agents, lines, webhooks and SIP trunks can be filtered by entity. The network's CRM or middleware retrieves everything entity by entity.
  • A SIP trunk dedicated to a single location automatically takes the entity of its lines.
08 Protected operations

An entity cannot be deleted by mistake.

Deleting an entitySchematic

Club B

  • Agents
  • Lines
  • Webhooks

Delete the entity

Blocked while it still holds items

Move its items in one action

  • Another entity
  • The account

Nothing is deleted

An entity that still holds items cannot be deleted. Its items are moved first, to another entity or to the account.

An entity that still contains agents, lines or webhooks cannot be deleted by mistake. Its items are moved in one action to another entity or to the account, never deleted.

09 Questions

Multi-entity voice AI, answered.

How long does it take to add an entity?

Minutes. You create the entity, then attach what already exists in one click from the dashboard lists. The shared agent is not redeployed.

Each of our entities has its own hours and offers. Is that handled?

Yes. Each entity keeps its own information: name, address, opening hours, phone numbers and local offers, while sharing the same agent.

How do I know which entity performs best?

Call logs, reports and consumption are filtered by entity, and a consolidated view of the network lets you compare entities with each other.

What if someone picks the wrong line?

The association is refused, whether it is made in the telephony settings, in an outbound campaign, in the dashboard or through the API. A line only works with the agents of its own entity or the agents shared across the network.

Who is responsible for an outbound call?

Each call leaves from a line of the entity it is placed for. The network knows which entity calls whom, which helps comply with GDPR and the EU AI Act and clarifies responsibilities.

Everything is already set up on our side. Do we have to redo it?

No, there is nothing to redo. You create the entities, then attach what already exists. Until an entity is created, nothing changes.

Our middleware has to follow. Can it?

Yes. The API filters agents, lines, webhooks and SIP trunks by entity, so your CRM or middleware retrieves everything entity by entity.

Can each entity have its own language?

Yes. An agent speaks one language, among French, English, Spanish, Dutch and Portuguese, so a network can mix languages.

Still have questions?

Contact us

Contact
Next step

See it on your own calls.

Book a call with a voice AI engineer: we start from your real call flows and show you the agent, the architecture and the numbers that fit them.

1:1with a voice AI engineer, no slides
2architectures we ship in production: speech-to-speech and pipelines
1rollout plan to leave with: volume, pricing, telephony

~0% missed calls at Bonnie&Car, down from 55%. Read the case study