Skip to main content
Pro plan. Calls are part of Meetings, and the call steps part of the AI assistant: both are in Pro and Agency (and the free trial). Each call step uses a few AI credits. See Plans and billing.
Every time you have a call with a contact, Kerux can follow up for you: check what kind of call it was, keep the details on the contact, and send the right email.

​
Where calls come from

​
Start a campaign when a call is recorded

  1. In the campaign, click + Add on the Trigger half of the start box and pick Call recorded (under Meetings).
  2. Pick where the call comes from (Any, Google Meet, Zoom, Another tool, Added in Kerux).
  3. Optional: Only calls longer than (minutes), to skip quick calls. A call of unknown length doesn’t pass this filter.
The contact enters once per call, as soon as the transcript is there (before the AI summary). To wait for the summary instead, use Call summary ready. Use these variables in the campaign’s steps: With Call summary ready, {{call.summary}}, {{call.interest}}, {{call.next_steps}} and {{call.follow_up_date}} are there too.

​
Call steps

Add them from + > Calls. They read the call that started the campaign, or the contact’s latest call with a transcript.
  • Ask AI about the call: a question with Yes / No / Not sure, or your own answers (for example “Demo”, “Pricing”, “Support”). Each answer is its own path on the canvas. Example: “Was this call a product demo?”
  • Extract from the call: list what to find in plain words, for example budget, decision maker, next step, 3 bullet points summary. Each value is a step output ({{steps.<step>.budget}}), and with Also save each value in the contact’s custom field of the same name it fills the contact’s field of the same name. Values the call doesn’t have stay empty, so a message that needs them waits (safe sending).
  • Draft the follow-up with AI: the AI writes an email from the call. By default it waits for you in My tasks > Follow-ups to approve: approve it as written, edit it, or decline it (the campaign then takes the declined path). Choose Use it right away only if you want it used without a review. Use the text in the next email step as {{steps.<step>.text}}.
What the people in the call said is information for the AI, never instructions: a sentence in the call can’t make the AI do something else. If something stops the contact:

​
Ready-made campaigns

Campaigns > New campaign > Build it myself > From a template (Browse templates), section After a call:
  • Demo call follow-up: the AI checks if the call was a demo. Yes: an email with your intro video (set the campaign variable intro_video_link). No or Not sure: a task for the contact’s owner.
  • Discovery call: budget, next step and pipeline: the AI saves the budget, who decides and the next step on the contact, moves the contact to Proposal and adds a task.
  • Thanks for the call: an hour after each recorded call, a short thank-you email.

​
Suggest a follow-up from a call

On the contact page’s Calls card, Suggest a follow-up asks the AI builder to draft a follow-up campaign from that call’s summary and next steps. It opens the draft with notes, like Create with AI. Nothing is launched until you do it.

​
Send calls from another tool

Meetings > Connected calendars > Call recordings > Other call tools > Create URL. Paste the URL in your tool’s webhook settings (or in a Zapier or Make step) and send JSON with these fields:
  • A call for someone who isn’t a contact is ignored.
  • When several contacts have that address, nothing runs: the call waits in My tasks > Calls to match until you pick the contact.

​
API and webhooks

  • POST /v1/calls adds a finished call (same fields as above, source_name for the tool). The answer says recorded, needs_review (pick the contact with POST /v1/calls/{id}/assign) or duplicate. If you transcribe recordings yourself, send source upload or recorded and the lines as segments (start_seconds, text) instead of transcript.
  • GET /v1/calls/{id} returns a call with its text; GET /v1/leads/{id}/calls lists a contact’s calls; GET /v1/unmatched-calls lists calls waiting for a contact.
  • POST /v1/calls/uploads and PUT /v1/calls/{id}/parts/{n} upload a recording in parts, when transcription on the server is available in your workspace (otherwise TRANSCRIBE_NOT_AVAILABLE: send the transcript to POST /v1/calls).
  • POST /v1/call-drafts/{id} approves (optionally edited) or declines a drafted follow-up.
  • Webhook call.recorded fires once per call and contact when the transcript is stored. See Webhooks.

​
Upload or record a call

On a computer, open the contact page’s Calls card and click Add a call:
  • Upload recording: pick an audio or video file (MP3, M4A, WAV, WebM, MP4…) of up to 2 hours.
  • Record: click Record the call, pick the browser tab or window of your online call and turn on sharing its audio, so both sides are recorded. Microphone only records just your microphone; Kerux says so while it records. Click Stop and add when the call ends.
Let everyone on the call know it’s being recorded. The call is transcribed on your computer: the recording never leaves your device, only the text with its timestamps is added to the contact. Then it works like any other call: Call recorded starts your campaigns, the call steps read it and the summary is written. Pick the call’s Language, or leave Detect automatically.
  • How long it takes: the first time, your browser downloads the transcription model (it keeps it for next time). A call usually takes a few minutes; older or slower computers take longer. You can close the panel and keep working, but keep the tab open.
  • Reloads and cancels: if the page reloads or you click Cancel, the contact’s Calls card shows the call that isn’t added yet. Click Open > Continue to pick up where it stopped, or Discard.
  • Phones and tablets: uploading and recording are on a computer. On a phone, paste the transcript instead.
  • Browsers: use a recent Chrome, Edge, Safari or Firefox. If your browser can’t transcribe, Kerux says so and offers Paste a transcript.