Any provider the Groundhogg SMS extension supports. The dashboard reads from gh_events and gh_activity, both of which Groundhogg writes regardless of whether the underlying provider is Twilio, MessageBird, or another carrier. The dataset is provider-agnostic so switching providers does not break the dashboard.

Delivery callbacks land when the provider's webhook is configured to call back into your Groundhogg site. Once the webhook is set up correctly, sms_delivered, sms_failed, and sms_undelivered events land in gh_activity with the matching activity_type and timestamp values, ready for charting.

Yes. The SMS broadcast type tags the send row in gh_events, while funnel-triggered SMS carry a step_id and funnel_id. Filter the dataset by the broadcast flag (or by funnel_id IS NULL) so the dashboard reflects only the broadcast layer if that is the audience that matters.

Yes. Aggregations run on the indexed columns Groundhogg maintains (contact_id, funnel_id, step_id, time, activity_type), so dashboards covering tens of thousands of SMS events render in seconds. The engine paginates and pushes filters into SQL rather than loading rows into PHP for counting.

Yes. Each chart card exposes its underlying row set, which exports to CSV with the active filters applied. That gives finance a clean monthly send-count export to reconcile against the provider invoice without manually counting rows in the Groundhogg admin.

If your SMS configuration writes STOP/UNSUBSCRIBE replies into gh_activity with a dedicated activity_type, the dashboard can chart those as a separate Donut slice or a dedicated KPI card. Opt-out rate over time is often a stronger list-health signal than a single broadcast's reply count.

Yes. Dashboard-level filters apply to every chart card. Scope the dashboard to a single funnel via funnel_id or to a contact segment via gh_tag_relationships and every chart reflects that audience without per-card reconfiguration. The same dashboard powers global and per-segment views.

Yes. Both extensions write into the same core tables (gh_events and gh_activity) with different step_type and activity_type values. The dashboard can render an email card and an SMS card side by side so omnichannel campaign performance lives on one screen across both channels.