Communications

Use Communications to understand the outbound messages ToolbagCRM sends for your company, including email, SMS, push, and voice notifications.

Communications is an always-on core feature. It is the shared delivery and audit layer used by ToolbagCRM workflows and optional plugins when they need to send a message.

The Communications page shows channel readiness and the shared delivery lifecycle used by reminders and workflow messages.

What the page shows

The Communications page summarizes:

• Supported channels — SMS, email, push, and voice.
• Delivery substrate — messages are queued before they are handed to a provider.
• Provider readiness — whether the channel is connected to a real delivery provider or still waiting on setup.

This helps your team tell the difference between a message being prepared inside ToolbagCRM and a message actually being accepted by an outside email, text, push, or phone provider.

How outbound messages work

When ToolbagCRM or a plugin sends a message:

1. The message is written to the communications outbox.
2. A background delivery job is queued.
3. ToolbagCRM selects the provider for the message channel.
4. The provider response is recorded back on the message for audit and troubleshooting.

The message lifecycle can include statuses such as Pending, Sending, Sent, Delivered, or Failed. A message can be Sent when the provider accepts it and later become Delivered when the provider confirms final delivery.

Supported channels

Channel	Used for	Notes
SMS	Text reminders, follow-ups, and workflow notifications	Requires a text-message provider before production delivery.
Email	System emails, workflow emails, and customer follow-ups	Can be connected to an email delivery provider for live sending.
Push	Mobile notifications	Depends on mobile app and push-provider setup.
Voice	Phone-call style notifications	Depends on voice-provider setup.

Why this matters

The Communications core keeps outbound messaging consistent across the product:

• Messages from different workflows follow the same queue and audit pattern.
• Duplicate sends can be avoided when a workflow retries the same logical message.
• Operators have a single place to check whether a message was queued, sent, delivered, or failed.
• Future plugins can use the same communication layer instead of each plugin inventing its own messaging process.

Current product notes

• Communications is always available in the main navigation.
• Some channels may show provider setup as pending until your account has the matching delivery integration configured.
• The Communications page is informational today; customer-specific send history and provider setup controls may appear in related workflow, billing, or settings pages as those areas expand.