Multi-channel sending
Start supported conversations from the customer record.
Use case · CRM publishers
Give CRM users one place to connect accounts, contact prospects, manage replies, and schedule the next step.
Project-scoped connection pathIllustrative CRM workspace; the supplied CRM and Outreach references share this composition.
Advanced CRM features
Move outreach, response management, scheduling, and account operations into the CRM surface your customers already use.
Start supported conversations from the customer record.
Keep replies, ownership, and follow-up state together.
Turn interest into a confirmed meeting without a context switch.
One interface, every channel
Let users move from prospect context to a real conversation without switching tools. One product surface can expose the connected channel, message history, delivery state, and the next action.
Shared response workspace
Collect replies in one structured inbox so teams can prioritize active opportunities, keep the full conversation history, and continue from the channel where the prospect answered.
Yes, I’d be happy to find a time.
Thanks for the context — let’s continue.
Thanks for the context — let’s continue.
Scheduling built in
Move from an interested reply to a meeting while the context is fresh. Show availability, create the event, and keep the booking result attached to the conversation.
MonTueWedThuFriSatSun
Account operations
Give each user a clear view of connected accounts and operational status. Project boundaries, provider identity, and recovery state stay visible before an outreach workflow runs.
Automated outreach
Create structured multi-channel sequences with delays, channel choices, and reply-aware stopping rules. Users can follow the whole campaign without losing sight of the person behind it.
Your extension captures. Your API enriches.
Begin with a project-scoped connection, select the supported events and actions, then return the normalized result to the product experience your users already know.
const account = await moira.accounts.connect({ provider: "linkedin", projectId: "project_recruiting", scopes: ["messages:read"],});await moira.webhooks.verify(account.event);Unified operations
Manage connected LinkedIn, WhatsApp, Gmail, Outlook, and calendar accounts from one operational view with explicit health, ownership, and recovery state.
Explore the APIOne operating layer
Use one project boundary for connection setup, supported actions, realtime evidence, and customer-controlled recovery.
Trust by design
Keep provider authorization outside the CRM with encrypted credentials, project isolation, and traceable customer-controlled access.
Frequently asked questions
Practical answers for product teams planning a connected communication workflow.
Users work from one customer record while messages, replies, booking state, and account health return to the same workflow.
Yes. The connected account remains explicit, and the maintained capability catalogue determines which actions are available.
Bind every connected account, API key, and webhook to its owning project and enforce that boundary server-side.
Quick start
Start with one customer conversation, verify the event path, and expand to sequences and scheduling.
Build now