Hybrid mode

Hybrid Outbound (hybrid mode) lets one API key own both Twilio and Blooio numbers and automatically pick which protocol to use per contact.

What it does

1. Cold outreach — first messages go out on Twilio SMS (cheap, high reach).
2. After they reply on that Twilio line — later sends switch to a Blooio iMessage number.
3. Optional transition text — on the first Blooio message, Blooio can send a short intro before or after your message (configured in the dashboard).

This is different from the manual “SMS blast, then tell them to text your iMessage number” pattern. Hybrid mode keeps one API key and one send call; routing flips for you.

Requirements

• The API key (or integration) has at least one Twilio number and one Blooio number assigned.
• Hybrid Outbound is enabled for that owner in the dashboard (Numbers / Channels hybrid controls).
• The send is 1:1 phone (not a group, email, or other identifier).
• You are not forcing a path that skips hybrid (for example an explicit from_number that takes you off the hybrid path — omit from_number for automatic hybrid selection).

If hybrid is off, or the key only has one protocol, normal number pool selection applies.

Send like normal

curl -X POST 'https://backend.blooio.com/v2/api/chats/%2B15551234567/messages' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{ "text": "Hey — quick question for you" }'

• No prior Twilio reply from this contact → Twilio sender from the hybrid group.
• Contact has replied on a group Twilio number → Blooio sender (sticky once chosen).
• First Blooio message may include your configured transition text (pre or post).

Configure in the dashboard

1. Assign both Blooio and Twilio numbers to the same API key (hybrid unlocks this mix).
2. Enable Hybrid Outbound for that key / hybrid group.
3. Optionally set a transition message and whether it sends before or after your first iMessage.

When not to use hybrid

• Pure iMessage product flows — use a Blooio-only key.
• Pure SMS / A2P campaigns that should never move to iMessage — Twilio-only key.
• Group chats — hybrid is 1:1 phone only.

Related

• Number pools
• Twilio integration
• Message sending

Hybrid Outbound (hybrid mode) is a routing mode for API keys that own both Twilio and Blooio senders. Blooio starts on SMS, then continues on iMessage after the contact engages.

What it does

1. Cold outreach — with hybrid enabled and no prior reply on the key's Twilio lines, POST /messages sends on Twilio.
2. After an inbound reply on one of those Twilio numbers — later sends use a Blooio sender (sticky once chosen).
3. Transition message — on the first Blooio leg, Blooio can inject configured intro text before (pre) or after (post) your content.

The send response includes routing.mode: "hybrid" and a hybrid object (phase, optional transition) so you can see which leg ran.

Requirements

• API key has Blooio + Twilio senders on its Channels priority (hybrid is disabled if other channel types are mixed in ways that invalidate it).
• Hybrid Outbound enabled for that key in the dashboard.
• Recipient is a single phone number (1:1). Groups and non-phone identities fall through to normal priority routing.
• Prefer omitting from so hybrid can choose. Exact from.number / from.id / from.type constraints follow normal sender resolution instead of the hybrid state machine when they pin a path.

Example

curl -X POST https://api.blooio.com/v4/messages \
  -H "Authorization: Bearer bl_live_..." \
  -H "Content-Type: application/json" \
  -d '{
    "to": "+15551234567",
    "content": { "type": "text", "text": "Hey — quick question for you" }
  }'

Typical response metadata when hybrid handled the send:

{
  "routing": { "mode": "hybrid", "channel_type": "twilio" },
  "hybrid": { "phase": "twilio" }
}

After the contact replies on SMS and you send again, channel_type / phase become blooio (and may include "transition": "pre" or "post" on the first iMessage).

Configure in the dashboard

1. On Channels, put at least one Blooio and one Twilio sender on the same API key.
2. Enable Hybrid Outbound for that key.
3. Optionally set the hybrid group name and transition message (before/after).

When not to use hybrid

• You always want iMessage — omit hybrid and use "from": { "type": "blooio" } or a Blooio-only priority.
• You always want SMS — "from": { "type": "twilio" } or Twilio-only assignment.
• Group messaging — use normal chat sends; hybrid does not apply.

Related

• Number pools
• Priorities
• Channels & senders
• Twilio integration
• Message sending