Go back to dialerseat.comsales@dialerseat.com
Start here

Build your integration with AI

No developer? An AI coding assistant can add DialerSeat to your CRM. Give it the prompt below and the docs it needs.


If your CRM is a web app you can change, with code an AI assistant can edit (your own app, or one made in an AI app builder), you do not need a developer to add DialerSeat. Give the assistant the prompt on this page. It reads the DialerSeat docs, looks at your code, tells you its plan and builds the integration in the sandbox, where nothing dials for real.

Does the AI not know DialerSeat already?

No. AI models learn from the web up to a date, and this API is newer than that. Asked from memory, an assistant guesses endpoint names that do not exist. The prompt sends it to two files written for it: https://dev.dialerseat.com/llms-full.txt, every docs page in plain text, and the OpenAPI description of every endpoint.

Five steps

  • Create a free project at dev.dialerseat.com. It starts in sandbox mode.
  • In the console, open API keys and copy your sandbox publishable key (dpk_test_) and create a sandbox secret key (dsk_test_). Open Webhooks and copy the signing secret (dswh_).
  • Put the secret key and the signing secret in your app's environment settings (in your app builder or your hosting), not in the chat. The prompt tells the assistant to read them from there.
  • Paste the prompt below into your assistant, with your publishable key. Read the plan it gives you before you let it change anything.
  • Try it: open a contact, click a test number, and check the result lands on the contact. When it works, switch the project to live in Settings and swap in your live keys.

The prompt

Paste into your AI assistant
You are adding the DialerSeat dialer to my CRM.

First read these, all the way through. Do not guess the DialerSeat API from memory: it is newer than your training data.
- https://dev.dialerseat.com/llms-full.txt (the complete DialerSeat developer docs as text)
- https://api.dialerseat.com/v1/openapi.json (every endpoint, as OpenAPI 3.1)

Then look through my CRM's code and tell me, in plain words, what you plan to change before you change it. Build this:
1. The miniplayer on the page where my users work their contacts, loaded with https://dev.dialerseat.com/embed/v1.js and my PUBLISHABLE key. Only the publishable key (dpk_) goes in the browser.
2. A server route that signs my logged-in user into the miniplayer: it calls POST /seats for that user (keyed on my own user id), then POST /seats/{id}/sessions, and hands the session token to the page. My SECRET key (dsk_) stays on the server in an environment variable called DIALERSEAT_SECRET_KEY. Never put it in browser code, in the repository or in a chat.
3. A way to send contacts to the dialer. Leads are not stored by DialerSeat: they travel with the session (up to 500 in the POST /seats/{id}/sessions body) or are handed to the miniplayer from the page. Each lead carries my own contact id as external_id and the phone number in E.164. Optionally tie my lists to campaigns with POST /campaigns, and use POST /campaigns/{id}/leads to check a list before sending it (it stores nothing).
4. A webhook route that receives DialerSeat's events, verifies the DialerSeat-Signature header with my webhook signing secret (dswh_) before trusting anything, and saves each call's result (disposition, duration, notes) onto the matching contact.
5. Click to call: data-dialerseat-call="+1..." on every phone number shown in the CRM.

Rules:
- Use my SANDBOX keys (dsk_test_, dpk_test_) until I say it works. Sandbox never places a real call.
- Test with the test numbers from the docs (the last digit decides: a person answers, voicemail, no answer or busy).
- If something in my CRM does not fit these steps, stop and ask me rather than inventing an endpoint.
- When you finish, give me a short list of what you changed and how I can try it.
Never paste a live secret key (dsk_live_) into a chat. If one ever ends up somewhere it should not be, revoke it under API keys; revoking is immediate.

Which assistants

Any assistant that can read a web page and edit your code works: a coding assistant such as Claude Code or Cursor, or the AI inside an app builder such as Lovable, Replit or Bolt. A chat that cannot edit your code can still write the code for you to paste in, one file at a time.

After it is built

To run DialerSeat from an assistant afterwards (add a seat, check a campaign, send a test webhook), connect it to the MCP server, described under OpenAPI and AI assistants. Each thing it does there is one API request made with your key.

Related:Quickstart, Tutorial: an HTML dialer, from nothing to paid, Developer accounts and Authentication and API keys.