Documentation
A practical guide to agent setup, knowledge, calling, review and billing.
1. Start with a single workflow
Choose the caller, purpose and information to collect. We agree the scope, dependencies and acceptance checks before implementation. Self-service console access is not part of this launch.
Discuss your workflow2. Give your agent a bounded job
In Voice AI Assistants, define the agent's role, short greeting, questions, escalation owner and stopping rules. Keep instructions specific: capture a viewing request and ask staff to confirm it, rather than promise an appointment.
Select a supported language and voice. Test names, numbers, interruptions and noisy audio in the actual provider configuration. Do not treat an edited draft as a deployed runtime.
3. Add approved knowledge and actions
Use current business facts, opening hours, service boundaries and FAQs. Remove unnecessary personal data. Decide what the agent should say when the answer is missing.
For a booking, CRM or custom API action, agree authorization, data fields, errors and human review. Verify both success and failure with controlled data before live use. A link to an integration is not evidence that the agent can already execute it.
4. Verify the number and calling route
Confirm number ownership, KYC, contact permission, account entitlement and provider readiness. Inbound needs its own route acceptance test. Neither the setup charge nor a saved agent automatically enables calling.
For campaigns, review CSV mapping and permission for each contact, suppression, calling window, concurrency and spending boundaries. Begin only with a specifically authorized small test. Review no-answer and failed results before approving any retry.
5. Review the call, not just the completion badge
Open Call Logs and inspect Chat, Replay, Analysis, Post Actions, Latency Profile and Debug Events where available. Confirm the correct caller and assistant turns, recording, terminal status, outcome and usage. Missing provider data remains unavailable rather than invented.
If a call is stuck or analysis fails, record the Dialit call reference and sanitized timestamps for support. Do not repeat a charge or place another call just to clear an uncertain state.
6. Understand setup and monthly capacity
Setup and monthly plan are separate payments. Check the full commitment, included minutes, concurrency, renewal and refund terms. No automatic renewal is created by setup checkout. Monthly minutes expire at cycle end; unapproved overage remains blocked.
After a payment, use the existing check-payment or secure onboarding-resume flow. If charged but not confirmed, contact support with the payment reference; do not pay again.
Review pricing and add-ons7. Launch with permission and an escalation owner
Document contact permission, opt-outs, recording notice, data access and retention. Test that the workflow refuses out-of-scope requests and reaches the right person when it cannot proceed.
For regulated sectors, obtain the relevant professional and provider review. The agent is not a medical, financial, legal or credit decision-maker.
Privacy policy Ask for launch support