AI voice with QCall

Current release · Updated October 2, 2026

Choose a workspace assistant and dialer for each reviewed outreach step.

Connect the workspace account

Choose AI voice/QCall in Connections and enter your own QCall API key. Save reads assistants and dialers without placing a call. The development testing key is local-only and is not distributed in public docs or production connections. Each production workspace supplies its own provider access.

Choose assistant and dialer

Select the assistant/dialer returned for this connection in every voice step. The reviewed contact must have consent and a valid international phone. At launch, DryKraft checks that the chosen options are still available. A voice campaign has one call step; a sequence can have multiple delayed steps.

Understand provider acceptance

For each recipient/step, DryKraft creates a distinct provider tag/contact and automated QCall campaign. Acceptance is not evidence that a call connected or completed. Voice call outcome callbacks, transcript analytics and voice reply-based stopping are not available in this release. Check the provider before creating another attempt after an unknown result.