SECURE ACCESS
Welcome back
Sign in to manage RCT messaging compliance.
RCT OUTSOURCING
Messaging overview
Sales Zoom accounts
Connect your own Zoom account to send from your assigned Sales number.
Compliance architecture
Every message passes the same server-side global check.
Saved records
| Customer number | Sales user | Message / contact | Status | Time | Reason / Zoom ID |
|---|
Sales user / Zoom number shows the latest recorded blocking source. Blocking applies globally to all four Sales senders.
| Customer | Sales user / Zoom number | Recorded by | Status | Reason | Source | Opted out | Sheet sync |
|---|
ONE LIST · ONE SALES SENDER
Create a CSV campaign
Upload your list, review eligibility, then start. Existing blocked numbers are filtered out before queuing. The backend sends eligible numbers one at a time at your chosen interval.
CHECK BEFORE SENDING
CSV preview
No CSV selected. Supported headers include phone, phone_number, mobile, or number. A single-column list without a header also works.
| CSV row | Normalized number | Eligibility |
|---|
Campaign queue
Progress persists on the server. Pause/resume never deletes your list or history. Failed API sends pause the campaign and are not automatically retried.
Recipient results
| Row | Number | Status | Reason / Zoom message ID |
|---|
Choose an action from the dropdown to move an inbox reply to Leads or block that customer across all four Sales senders. Reply history stays saved. Admin access is required.
| Customer | Received on | Latest reply | Status | Received | Actions |
|---|
SERVER-SIDE PROTECTED