iCallAgent

Appearance

Slack ​

Connect Slack to place calls straight from a conversation. Mention the bot or DM it in plain English, and it queues the call after confirming the details with you.

Connecting ​

From Integrations in the dashboard, connect Slack via OAuth2 (standard Slack app install flow). This binds a Slack workspace to an iCallAgent workspace.

Ways to trigger a call ​

  • @mention or DM: @icallagent call Stephan at +1 555 123 4567 and tell him the invoice is overdue
  • Slash command: /icallagent call Stephan about the invoice

Both go through the same natural-language intent parser and end at the same confirmation step. The slash command is just a shortcut into it.

How it works ​

  1. Your message is parsed to extract the call intent: who to call, a phone number and/or a contact name, and what the agent should say.
  2. Extracted details are resolved against real data: a phone number/contact name against your Contacts, an implied agent against your Agents.
  3. If something's missing or ambiguous (e.g. more than one contact matches, or no agent was specified), the bot asks a clarifying question, as clickable buttons when there's a fixed set of choices (e.g. picking which agent), or as a follow-up question otherwise.
  4. Before queueing anything, the bot always shows a confirmation summary and waits for you to approve (yes/confirm, or the Confirm button) or cancel (no/cancel).
  5. On confirm, the call is queued through the exact same path as the Make.com Send Contact module (POST /contacts/), so it follows the same compliance checks (blacklist, do-not-call, consent) as every other call.

A conversation is scoped per Slack user and channel, so you can have independent in-flight call requests in different channels without them interfering with each other. Conversations go stale after a period of inactivity, so an abandoned draft doesn't linger indefinitely.

Resolving a campaign by name ​

If your message references a campaign by name rather than starting one from scratch, the call is queued into that campaign directly, using the same name-matching behavior as the campaign field on POST /contacts/.

Security ​

Inbound requests from Slack (events, slash commands, button clicks) are verified against Slack's request signature before anything is processed.