Skip to main content
Ara supports iMessage-style communication through two different bridges.

​
Option A: native Mac bridge

Best when you use Ara desktop and want local iMessage integration.

​
Flow

  1. Desktop app receives iMessage events from macOS
  2. Events are forwarded to your cloud session/runtime
  3. Runtime generates response
  4. Desktop app sends response back through Messages

​
Tradeoff

Desktop app must be online for message relay.

​
Option B: Linq channel bridge (always-on)

Best when you want cloud-native, always-on messaging with protocol fallback. Linq supports:
  • iMessage
  • RCS
  • SMS fallback

​
Flow

  1. Incoming message hits Linq webhook
  2. Webhook event is processed by runtime channel adapter
  3. Runtime responds through Linq API
  4. User receives message on best available protocol

​
Setup guidance

1

Choose bridge mode

Decide between desktop-native bridge and Linq cloud bridge.
2

Configure credentials

For Linq, configure token and from_number; for desktop, ensure macOS account permissions.
3

Validate with test thread

Send a test message and confirm full round-trip response.

​
Recommendation

  • Use desktop bridge for personal local workflows.
  • Use Linq for 24/7 autonomous communication and iMessage/RCS/SMS continuity.