Bring the context.
Provide inbound inquiry, crm accounts and lead history, territory and ownership rules. Choose the systems and documents this team is allowed to read.
Match an incoming inquiry to an account, territory and owner so the next conversation starts informed.
Illustrative output. Your records and rules shape the workflow.
Bring context from the tools your team already uses. Connect MCP servers and APIs to read records, coordinate actions and keep the evidence together.
Explore the request, the responsibilities and the handoff. Each step keeps the source context attached.
Corin uses the request together with the procedures and records you make available to this workflow.
These example roles show how the work can be divided. Review the proposed team, models, tools and permissions for your process.
Find the account and check for an existing lead, customer or active deal.
Apply territory, segment and ownership rules to propose the correct owner.
Prepare a handoff with the request, account context and any ambiguity.
The result includes its source context so the responsible person can review it and decide what happens next.
A new lead submits a form or arrives by email. The team needs inbound inquiry, crm accounts and lead history and territory and ownership rules to make the next step useful.
Start with the procedure your team already follows. Corin uses that context to propose responsibilities and help coordinate the work across the tools you connect.
Provide inbound inquiry, crm accounts and lead history, territory and ownership rules. Choose the systems and documents this team is allowed to read.
Use lead context agent, routing agent, handoff agent as a starting point. Set each role's tools, permissions and approval boundaries.
Run a representative task. Compare the result with your procedure, review its sources and open questions, then refine the team before expanding the workflow.
Give Corin your procedures, connected context and approval rules. Review the agent team, then put it to work.