Settings

What this deployment is connected to and how safely it sends. Read on every request, so this screen reports the real state — and what is changed here takes effect on the next message, with no redeploy.

AI

One switch for everything that acts without a person. Off, this is a collections management system your team runs by hand.

AI is off
Your team runs every case: replies wait under Needs a reply, calls play the scripted message, and outcomes are recorded by hand.
Replies to texts
Your team answers
Calls
When a call is answered.
Scripted message
Outcomes
Promises, payments, disputes, wrong numbers.
Recorded by your team
Journeys
Scheduled texts and calls — rules, not AI.
Run either way

Either way, your team can text a customer, record an outcome or log a call from any case, and it lands in the same records the agent writes to — so reports read the same whichever did the work.

Send safety

Who this platform is allowed to reach.

Only allowlisted numbers receive messages
1 number cleared. Everything else is held and recorded.

Nothing loaded can be texted yet. With reach at Anyone, an upload's customers are texted and called as soon as a journey runs. Set here, this outranks the deployment’s own setting; clear it and the deployment default takes over again.

Allowlist
Only these numbers receive anything while reach is Allowlist.
+97339112829
1 number

Edit the list with SMS_ALLOWLIST in the deployment, or switch reach to Anyone above.

Sender

What a customer sees when a text or a call arrives.

Text sender
Set here

What a customer sees a text arrive from — a messaging service, a number, or a registered sender ID.

Replies cannot reach a sender ID. Texts go out, but nothing comes back — the agent will never see an answer.

Sender ID — one-way, no replies7/11

Caller ID
Set here

The number shown when the platform calls. Must be one the account owns or has verified.

Bahraini number — calls go out over the Batelco trunk

A messaging service carries the sender registration, per-country selection and opt-out handling, and customers can reply to it. A short sender ID such as “Batelco” is the recognisable option for Gulf A2P, but it is send-only — replies never arrive, so the agent cannot answer, and promises and disputes stop coming back. Changed here, it takes effect on the next message; no redeploy.

Payment links

Where the link in a text takes a customer to pay.

Active lines
Batelco default

A line that is still connected pays through Batelco eServices.

Sent to 2 open cases

Ceased lines
Batelco default

A line that has been cut off pays through QuickPay for ceased accounts.

No open cases get this link today

A line counts as ceased when it arrived in a cease or referral file, or its cease date has passed; every other line gets the active link. The same link goes out in journey texts, the agent’s replies and your team’s. A payment made on Batelco’s pages doesn’t report back here — use Record payment on the case, so its journey stops asking.

Agent

The AI is off — nothing here runs until it's back on.

Mode
From the environment, or auto if unset.

Live when a key is present, lite when it isn't — currently resolving to live.

Running
Live
Model key
Needed only for live mode.
Present
Model
Hosted

Lite mode is not a mock. It writes the same promises, disputes, escalations and signals to the same tables and passes the same guardrails. What it gives up is free-text handling: replies outside the scripted branches go to a person rather than being improvised. Use it when a demo must not depend on the network, or to run at no model cost.

Text messages

Channel
Texts leave the platform and reach real handsets.
Live network
Credentials
Present
Sender
A registered sender, which Bahrain A2P expects.
Messaging service
Sending pace
The network's rate for texts to Bahrain, counted in message parts. Journeys, the agent's replies and your team's share it, so nothing queues at the network — a thousand two-part texts take about 3 minutes.
10 parts a second

Voice calls

Channel
Calls are placed to real handsets.
Live network
Conversation
Listens in real time, in Arabic or English, and can be interrupted mid-sentence.
Conversational agent
Speaking voice
A Bahraini voice reads every reply, with amounts and dates said the way Bahrainis say them. Each sentence is checked against the guardrails before it is spoken.
Ruba — Bahraini
Caller ID
The number customers see. A Bahraini number, so calls go out over the Batelco trunk.
+97317251420
Calling pace
New calls a second — the account's limit, shared by journeys and campaign calls.
1 a second
Campaign calling
Numbers entered on the Campaign screen are dialled directly, bypassing the allowlist. Journeys still respect it.
Any number
Answering-machine detection
The agent decides; detection is recorded, not obeyed.
Advisory

The biggest disclosure risk on a collections call is leaving the amount on a voicemail someone else plays back. The protection that holds is ordering: nothing states the balance until a person has answered and confirmed who they are. With the conversational agent connected the machine verdict is advisory — it has been seen calling a live person a machine — so the agent hears the same audio and ends the call itself on a voicemail.

Webhooks

Where the carrier reports replies and call events. Every endpoint rejects a request whose signature doesn't verify.

Public base URL
The carrier signs the exact URL it called; behind a proxy the internal URL differs, so signatures fail without this.
Set
Inbound texts
POST https://smartcollect.doo.space/api/webhooks/sms/inbound
Text delivery receipts
POST https://smartcollect.doo.space/api/webhooks/sms/status
Call answered
POST https://smartcollect.doo.space/api/webhooks/voice/answer
Caller input
POST https://smartcollect.doo.space/api/webhooks/voice/gather
Call status
POST https://smartcollect.doo.space/api/webhooks/voice/status

Without signature checks anyone who learned a URL could forge a customer reply — logging a promise or raising a dispute on someone else’s account.

Message templates

13 messages, each in Bahraini Arabic and English. Open one to edit it — changes reach the next text sent.

P1 Early Dunning
P2 Smart Follow-Up
P3 Recovery
Promise to pay

Every edit is held to the same guardrails as the agent’s own replies before it can be saved, and checked again just before each text is sent. A message may state the interruption date — only the day-12 notice can — and nothing beyond it: no legal, court, credit-bureau or agency language. Reset returns a message to the approved wording.