What is GodSetter?

GodSetter gives your agency AI voice agents that call your CRM leads, qualify them and book real calendar appointments — automatically, at scale, and under your rules.

What it does

• Outbound calling — a workflow in your CRM triggers a call to a new lead within seconds: the first call is dispatched the moment the lead arrives, and the every-minute dispatcher is only the safety net. The AI agent speaks naturally, follows your prompt, and works toward one goal: booking a qualified appointment on the right calendar.
• Inbound handling — when a lead calls back one of your numbers, the dedicated inbound agent you paired with the agent that called them answers; otherwise the outbound agent that opened the cycle does. Either way the agent has full context, written by the platform and not by your prompt: who is calling, who had called them and why, previous call outcomes, and their upcoming appointments (so it can answer "when is my appointment?", cancel the right one, or reschedule it).
• Appointment booking — the agent reads real free slots from the client's calendar, books directly, and guards against double-booking by re-checking the slot immediately before confirming.
• CRM write-back — after every call GodSetter tags the contact by outcome (booked, not interested, callback, no answer…), adds a call note with the summary, and can fill custom fields you map (budget, timeline, anything the AI extracted). Your CRM automations key off those tags.

How it fits your agency

GodSetter is multi-tenant and agency-first:

• Your agency connects its own providers once: the voice engine (Retell), the telephony carrier (Twilio) and your CRM (OAuth). Calls bill your own accounts — no shared pools.
• Your clients are CRM sub-accounts, auto-imported daily and active from the start. Each one books into the calling agent's default calendar, or into a calendar of its own if you pick one.
• Your agents are reusable templates: one prompt per campaign, shared across clients, with versioning, A/B metrics per prompt version, and one-click rollback. Each agent is also outbound or inbound: outbound agents open call cycles, inbound agents only answer. You state the pairing yourself — an inbound agent lists the outbound agents whose call-backs it answers — so nothing is inferred from a name or a number.
• Your numbers are bought in-app, registered on your Retell account automatically at purchase (a number Retell does not know can neither dial nor receive), and assigned per agent, so a UK campaign never dials out from an Italian number.
• Your team works in the same console: invite colleagues as admin or collaborator, and give a collaborator access area by area (disabled / viewer / editor) plus a separate permission to spend money.

Built-in guardrails

• Calling window — outbound calls only happen inside the schedule you set (hours, days, timezone). Everything else waits.
• Retry cadence — no answer or voicemail? The agent retries on your schedule, up to your cap. Voicemail detection hangs up instead of talking to a machine.
• Do-Not-Call — if a contact asks never to be called again, GodSetter blocks the lead everywhere: no retries, no new triggers, no inbound answer. Only an operator can unblock.
• Consent strict mode — optionally require valid consent proof on every lead before any call fires.
• Concurrency and saturation — a per-agency cap on simultaneous calls, capped in turn by your Retell plan, with a slice reserved for first calls and agreed callbacks so a retry backlog can never starve a fresh lead. You also get alerts when your number pool is running hot.

Where to go next

1. Wire your CRM workflow to an agent — the 10-minute setup that starts your first calls.
2. Calls are not firing — full checklist — if you set things up and nothing dials, this finds why.