Skip to content

Known caveats

These are the behaviors to know before you turn on RingCentral for customer messaging.

TracsConnect needs RingCentral app credentials, not just your regular RingCentral username and password. Someone with access to the RingCentral Developer Console needs to set that up first.

Use Sandbox only for testing. Use Production for the live RingCentral app and live phone number. Mixing the two is the most common setup mistake.

The sender number must be able to send texts

Section titled “The sender number must be able to send texts”

If RingCentral has not enabled texting on that number, TracsConnect may connect successfully but messages will still fail. Confirm texting is allowed on the number before going live.

The form treats the sender number as optional, but sending does not

Section titled “The form treats the sender number as optional, but sending does not”

The dashboard can save the connection without a sender phone number, and the credential test can still pass. TracsConnect’s RingCentral messaging provider requires that number before it can send. It does not fall back to an account default.

TracsConnect stores your RingCentral sign-in details and can send outbound texts through your RingCentral account. That is what is working and tested.

TracsConnect does not send RCS messages through RingCentral. Texts go out as standard SMS or MMS.

Inbound replies require webhook provisioning

Section titled “Inbound replies require webhook provisioning”

TracsConnect has a RingCentral inbound-message webhook, but the dashboard setup window does not create the RingCentral subscription that delivers events to it. Until support confirms that subscription is provisioned for your rollout, monitor replies in RingCentral.

Call activity also requires webhook provisioning

Section titled “Call activity also requires webhook provisioning”

TracsConnect has a RingCentral telephony webhook pipeline, but the basic credential setup does not provision it. Continue managing calls, missed calls, voicemail, and recordings in RingCentral unless support has explicitly enabled and verified call ingestion for your rollout.

What Current status Notes
Outbound texts Live Sends through your RingCentral account.
Sender phone number Required for sending The form can save without it, but the messaging provider cannot send.
Customer replies Rollout-dependent Requires a separately provisioned and verified webhook subscription.
Delivery receipts Not in TracsConnect Check RingCentral for carrier-level delivery detail.
Call activity Rollout-dependent Requires separate webhook provisioning; continue managing voicemail and recordings in RingCentral.
RingCentral users and billing No sync Manage in RingCentral.

Sending volume limits are not documented yet

Section titled “Sending volume limits are not documented yet”

RingCentral limits how many messages can go out in a given window. The exact limit and how TracsConnect handles large batches need verification before your shop relies on bulk sends.

The current Connections page does not provide a self-service RingCentral removal action. Contact support to remove the connection, then verify the shop’s messaging provider before sending again. Past messages are not deleted by removing credentials.

If RingCentral and another TracsConnect texting provider are both set up, decide which one sends appointment reminders. Sending from two places will double up and confuse customers.

No. Sandbox is for testing only. Use Production for live customer messages.

Can I share one RingCentral app across several shops?

Section titled “Can I share one RingCentral app across several shops?”

Use a separate app per shop unless TracsConnect support confirms a shared-app setup works for your rollout. Separate apps make it much easier to troubleshoot and rotate credentials.

Do I need a dedicated RingCentral number for TracsConnect?

Section titled “Do I need a dedicated RingCentral number for TracsConnect?”

Not necessarily. You need a number that is allowed to send texts on your RingCentral account. Whether it should be dedicated depends on your setup and how you want customer replies handled.

The troubleshooting page covers the common cases. If something is not there, contact support with the date and time, the last four digits of the sender number, and what you expected to happen. Never send your Client Secret or JWT Token to support.