LoginSign Up
← Back to all sparks
C

Customer.io

MKT AUTO
Velocity7.5

Customer.io is turning messaging context — location, knowledge, carriers — into platform primitives

geofencingllm-actionsmulti-channel-messagingdelivery-controlsplatform-primitives
◆Current state
Customer.io came out of a summer wave carrying more than ten features, and the ones that matter reshape what a message can be triggered by and what it can know. Geofences make physical location a native trigger, reusable knowledge sources give LLM actions a workspace-scoped context layer, and SMS opens to Sinch, Infobip, and Vonage alongside Twilio. The most recent entries turn to control and craft: per-channel rate limits, and a rebuilt Design Studio canvas.
◆Where it's heading
The pattern is absorbing things customers previously bolted on — third-party geofencing, per-prompt context pasting, a single mandated SMS carrier — and making each a configurable primitive inside the platform. Delivery control is following the same path, with rate limits and wait-before-continuing giving operators throttles they would otherwise build around. Each move reduces the surface where an integration or a workaround was required.
◆Prediction
Expect the knowledge layer and the Agent to converge further, since knowledge sources were already extended to the Agent on release, and expect more delivery-side controls now that rate limiting exists per channel. The plan gating on geofences suggests newer primitives will keep landing on Premium and Enterprise first.

◆Recent moves

  1. 5d ago

    Design Studio: new and improved canvas editing experience

    The Design Studio canvas gets slash commands for adding blocks, navigation and resize shortcuts, and drag from anywhere on a component rather than only its handle. Editor craft rather than new capability, but it lowers the cost of building the components the rest of this window's features send.

    View source ↗
  2. 13d ago

    Control how fast your automations send messages

    Per-channel rate limits land for automations and API-triggered broadcasts, with an option to hold a journey until the message is delivered. It gives operators a throttle for sender reputation and downstream load that previously had to be engineered around the platform.

    View source ↗
  3. 20d 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 expanded SMS support, all of which appear as their own entries in this window.

    View source ↗
  4. 20d ago

    Add reusable knowledge sources to LLM actions

    ⚡ SPARK

    Prompt context moves out of individual LLM actions and into a workspace-scoped Knowledge Library that actions and the Agent both draw on. It converts repeated prompt text into a reusable, named resource — the shift from prompt-writing to context management.

    View source ↗
  5. 20d ago

    Geofences: message people when they enter or exit a location

    ⚡ SPARK

    Physical location becomes a first-class trigger alongside events and dates, with geofence crossings driving automations, segments, and wait conditions. It is the clearest example of the pattern in this window: a capability customers previously integrated for, pulled inside the platform.

    View source ↗
  6. 20d 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. It removes a single-vendor constraint for teams messaging across regions or subaccounts, matching the window's broader move away from mandated integrations.

    View source ↗