Skip to main content
Audact
See the offer

Integration · Slack

The alert arrives where your team already is.

Integration · Slack: In development

In development: Audact would post a structured message the moment something needs a person: a refused utterance, a dial blocked by eligibility, an escalation to a human, an evidence-export request. Channels would map per sub-account, so an agency supervising a dozen end-clients would not need a dozen dashboards — or a dozen channels going off at once.

What lands in the channel

{
  "text": "Governance gate — blocked",
  "blocks": [
    { "type": "section", "text": "*acme-dental* · sess_8h2k9d7" },
    { "type": "section", "text": "policy=commercial_commitment · severity=hard" },
    { "type": "context", "elements": ["receipt rcpt_gov_01HX7… · 15 Aug 10:14"] }
  ]
}

Worked example. Acme GmbH and Nova Industries are fictional; no customer data appears here.

Every alert carries the receipt id, so the message is a starting point rather than a summary you have to trust.

What it sends

Would surface refused utterances and scope-of-practice interventions, as they happen.
In development
Would report dials blocked by the eligibility check, with the reason code.
In development
Would route escalations to a human.
In development
Would announce a request for an evidence export in the channel.
In development
Would send daily and weekly digests, per sub-account, for what does not need an interrupt.
In development
An enquiry submitted through the enterprise form on the Audact website is posted into a Slack channel of ours. That is Audact notifying itself, not the voice product posting into your workspace.
Working today

Setup

Planned setup

In development

  1. Authorise Audact in your Slack workspace, or paste an incoming-webhook URL.
  2. Map sub-accounts to channels. One per end-client keeps the noise where it belongs.
  3. Choose which event types interrupt and which only appear in the digest.
  4. Fire a test event from the Audact console and confirm it lands.

Questions

Does personal data go into the Slack alerts?
In development: no. Alerts would carry identifiers and reason codes, not transcripts and not caller details. What you need to act on would be in the message; what you need to read would be behind the receipt id.
Can end-clients see their own channel?
In development: if you invite them. The mapping would be per sub-account, so an agency could keep a client-facing channel and an internal one side by side.

The same events, as a dashboard

The observability layer shows the same stream with history, filters and export, for when an alert is not the right shape.

See the observability layer

Related