Skip to content
Verbatik
GuidesAPI reference

Getting started

Build your calling workflow

Set up AI voice and chat agents, connect your tools, and bring them to your clinic’s phone and website.

Build your first agent

Set up a workspace, add your knowledge and try a browser call.

Connect your phone number

Choose forwarding or SIP while keeping your existing carrier.

Connect your booking system

Authorize a calendar and verify a complete appointment journey.

Build with the API

Use scoped API keys, webhooks and verified request examples.

Start with a browser call

Create your workspace, choose an agent template and add the information your team normally gives callers. Test the conversation in your browser before connecting a public phone number. The quickstart takes you through the full sequence.

How Verbatik fits together

  1. Workspace: your team, contacts, agents, connections and call records stay together. Use a separate workspace for each client or clinic that needs separate access.
  2. Agent: instructions, voice engine, language, knowledge and approved tools define the conversation. Save changes as a draft, test them, then publish a version.
  3. Connection: authorize your own calendar, CRM or document service. Attach only the tools and knowledge sources the agent needs.
  4. Channel: receive calls through a number or SIP connection, or embed a voice and chat widget on your website.
  5. Flow: trigger follow-up steps from a lead, wait, call an approved contact and branch on the result.
  6. Review: use history, transcripts, tool receipts, analytics and quality checks to verify what happened.

Choose your setup path

  • Clinic receptionist: start with onboarding, connect bookings and follow the go-live checklist.
  • Keep an existing number: compare forwarding and SIP, then use the guide for your carrier.
  • Website voice and chat: configure and install the widget.
  • Lead follow-up: begin with the 10-second lead flow and verify consent and channel readiness before activating it.
  • Developer: create a scoped key and use the API reference. Never put a secret API key in a website or widget.

Before you launch

A browser conversation checks the agent’s behavior. A phone launch also needs a ready number or carrier, a published agent, account approval for the channel and an end-to-end test. Booking requires access to the actual scheduling system; a general calendar is not automatically your clinic’s practice-management system.

Outbound calling and SMS have separate activation requirements. If the dashboard reports a channel unavailable, complete the relevant phone or SMS setup prerequisites before relying on it.

Find an answer

Use the search at the top of the page or press Ctrl K / Command K. Every guide is available as Markdown using the copy-page control. If a provider requires partner access, its integration guide explains which access to request and how to test it once approved.

Verbatik documentation · Updated November 5, 2026
Next

Build your first agent