Sofia
Add a workforce agent
One agent per store. Configure the VM from Sofia → Add a workforce agent. A local number is bought when provisioning is live; until then the job queues.
One workforce agent per store. The agent is the VM and the number staff call. Admins add it from Sofia → Add a workforce agent.
A local number is bought when provisioning is live. Until then the job queues — nothing is purchased. The public line is boarding.
Before you start
- You are an admin.
- The location exists. Add stores in Settings.
- Billing is $200 USD per store per month. Subscribe from Settings if you have not.
Configure the agent
The wizard asks for:
- Location — one agent per store.
- Voice runtime — Grok Voice (policy engine in Sofia, Grok on the VM edge) or Hermes + ElevenLabs (roster writes still go through Sofia).
- Region —
us-east4,us-central1, oraustralia-southeast1. The VM ise2-standard-2with a 30 GB disk. Operator SSH only; customers do not get a shell. - Number country and optional area code.
- SMS on the same number, workflows (which of late / cannot-make-it / named swap auto-execute vs log), and roster source (Sofia or Tanda).
Confirm. If GCP and Twilio secrets are not set, the job queues — nothing is purchased. When they are set, Sofia buys a local number and creates the VM. A failed job can be retried without buying a second number.
After it exists
Open Voice settings for the greeting, who Sofia offers, the E.164 number, Tanda location mapping, and the kill switch.
Put the number on the staff noticeboard only when it is actually on the store. A boarded line that still queues is not a 6am backup yet.
Remove
From the Sofia screen, admins can remove an agent. Queued and boarding jobs drop. When secrets are set, a bought number and VM are released. The kill switch is the reversible "stop answering" control — prefer it during an incident.