LoginSign Up
← Back to all sparks
C

Customer.io

MKT AUTO
Velocity7.5

After a summer of new send surfaces, the controls arrive: per-channel rate limits and send pacing.

geofencingrate limitingdevice surfacesbyo smsllm knowledgejourney control
◆Current state
Customer.io spent the summer widening where a message can land — geofence triggers, Live Activities, an in-app notification inbox, multiple mobile apps per workspace — and loosening who carries it, with Sinch, Infobip, and Vonage joining Twilio for SMS. The newest release turns to governance: per-channel rate limits on automations and API-triggered broadcasts, plus a wait-before-continuing step that holds a person in a journey until the message actually lands. The LLM layer picked up reusable knowledge sources, moving prompt context out of individual actions into a workspace-scoped library the Agent can also read.
◆Where it's heading
The pattern is surface-first, control-second. Each new channel widens the blast radius, and the rate-limit release reads as the answer to customers hitting the ceiling of their own sender reputation and downstream systems. Expect reach features to keep arriving paired with the guardrails that make them safe to switch on at volume — per-channel budgets, delivery-aware waits, activity logging on every new trigger type.
◆Prediction
The next likely move is extending rate limiting and the wait-for-delivery step from automations to the remaining send paths, and giving geofences and live notifications the segmentation and reporting depth email already has.

◆Recent moves

  1. 6d ago

    Control how fast your automations send messages

    Per-channel rate limits and a wait-before-continuing step land immediately after a quarter of surface expansion — the throttle that makes the wider send footprint safe to run at volume. It targets the two failure modes of high-cadence automation named in the note: sender reputation and downstream systems that cannot absorb a burst.

    View source ↗
  2. 13d ago

    Set up SMS with Sinch, Infobip, or Vonage

    Sinch, Infobip, and Vonage join Twilio as SMS carriers, with more than one provider allowed per workspace. This is lock-in loosening rather than new capability — the same message, more routes, and easier coverage across regions and subaccounts.

    View source ↗
  3. 13d ago

    Add reusable knowledge sources to LLM actions

    ⚡ SPARK

    Prompt context moves out of individual LLM actions and into a workspace-scoped library the Agent can also read — the step that makes the AI layer stateful rather than a per-action text box, and the one piece of the summer wave aimed inward at how campaigns are built rather than where they land.

    View source ↗
  4. 13d ago

    Geofences: message people when they enter or exit a location

    ⚡ SPARK

    Physical location becomes a first-class trigger alongside events and dates, with enter/exit conditions usable in segments and wait steps and recorded in activity logs. It is the sharpest expression of the arc away from inbox delivery and toward device-resident context.

    View source ↗
  5. 13d ago

    Summer release roundup indexing ten-plus features

    An index post for the summer wave rather than a release of its own — it points at geofences, live notifications, the notification inbox, and the expanded SMS provider list, each of which appears separately in this timeline.

    View source ↗
  6. 14d ago

    Send push notifications to multiple mobile apps in one workspace

    Registering several apps per platform in one workspace retires the workaround of splitting audiences across workspaces, and profiles can now be segmented by which apps they use. Plumbing that makes the summer's wider push surface usable for companies shipping more than one app.

    View source ↗