Channels · AI Phone CallsStatus: Planned

AI Phone Calls.
Natural conversations, a person on call.

A planned concept for answering inbound calls and, where authorised, placing consented outbound calls — with calling windows and a transfer to your team. Telephony is a future integration; this page makes no calls and plays no audio.

Explore ChannelsSee how it works

Concept Preview · Illustrative demos · Availability not confirmed

Voice console conceptIllustrative Demo
Calling windowConsentHuman transfer

MOCK TRANSCRIPT · INBOUND RECEPTION

  • CallerHello, are you open on Friday?
  • AI assistantHi, you're speaking with an AI assistant for Sample Clinic. We're open Friday afternoon. Would you like a teammate to book a time?
  • CallerYes, please.
  • SystemTransfer to front desk (sample)

No microphone, call, audio, recording or telephony provider. Transcript is sample text.

Use cases

Where AI Phone Calls could help.

Reception

Greet callers, answer common questions and take messages.

Appointment requests

Capture a preferred time for your team to confirm.

Authorised confirmations

Outbound confirmation calls only to contacts who agreed to be called.

Transfer to a person

Pass the caller to a teammate when they ask or the call needs judgment.

Capabilities

Designed around your team.

Proposed capabilities aligned with the REBNAL platform. None are live on this channel yet.

Approved scripts & knowledge

Calls follow reviewed business information, never improvised policies.

Calling windows

Outbound calls are designed to happen only within permitted hours.

Human transfer

A clear route to your team, with a summary of the call so far.

Call outcomes

Record what happened and the agreed next step for your team.

How it works

Four steps, with a person in the loop.

Workflow Demo · Not Live

  1. STEP 01

    Call begins

    An inbound call, or an authorised outbound call within a calling window.

  2. STEP 02

    Understand the need

    The concept agent identifies the request using approved knowledge.

  3. STEP 03

    Transfer or resolve

    Hand over to a teammate or capture the request.

  4. STEP 04

    Record the outcome

    Log the result; any callback needs consent and approval.

Handoff & permission checkpoint

A caller ID is not verified identity. Outbound calls need recorded consent, calling-window checks and approval.

Privacy & platform safety

Responsible by design.
Confirmed before launch.

Proposed safeguards. Actual compliance, security and retention details need confirmation before any launch.

Consent before outbound

No outbound call without recorded, purpose-specific permission in the proposed design.

Calling windows

Respect local permitted hours and do-not-call requests.

Clear AI disclosure

Callers should know they are speaking with an AI assistant and can ask for a person.

Questions & answers

A little more clarity.

What to expect from these channel concepts, and what still needs to be confirmed.

Explore other channels

Part of REBNAL Channels

One conversation.
Every channel connected.

See how AI Phone Calls fits into the wider Channels vision, or start with Website Chat.

Back to ChannelsDiscover Website Chat