The agent collects requests from email, Telegram, and forms, sorts them by type and urgency, logs them to a CRM, and notifies the owner. Urgent ones escalate to a human.

For new users: your first ASCN subscription payment doubles the term. [Use template] [Ask a question]
Requests land across email, Telegram, and website forms — and someone burns an hour a day copy-pasting them into a spreadsheet, guessing the priority, and forwarding to the right teammate. Things slip; an angry customer waits a day. A part-time ops coordinator costs $600–1,500/month.
Inbound Request Router is a ready-made AI agent for the ASCN platform that handles intake for you:
You run it in plain chat. Every request and its history live in your Google Sheet.
No coding. You run everything from a chat.
Across setups, the agent takes about an hour a day of manual intake off the team and cuts the time for an urgent request to reach the right person from hours to minutes.
The effect depends on your inbound volume and how the routing matrix is set up. The agent delivers fast sorting and hand-off — the quality of the reply to the customer stays with your team.
Online store — retail
- Connected: Gmail, Telegram, Google Sheets, a 3-person matrix
- Result: requests sorted by type, complaints escalated to the owner
- Effect: urgent messages reach a human in minutes instead of hours
B2B service — services
- Connected: Gmail (site forms), Telegram, CRM in Sheets
- Result: purchases → sales manager, partnerships → founder
- Effect: about an hour a day saved on manual sorting
Agency — multiple departments
- Connected: Telegram, Gmail, a per-department matrix
- Result: every request with the right team, spam filtered out
- Effect: a clean queue — people see only real requests
Figures are illustrative — an expected effect for the niche, not a guaranteed result.
While inbound drowns in a shared inbox and chat, hand intake to an agent that sorts it, logs it to the CRM, and gets urgent things to the right person. 🔥🔥🔥
Set the team up once — and the inbound stream sorts itself, with nothing lost and nothing delayed.
Do I need coding skills?
No. The agent installs from the marketplace and is set up in plain chat: name your channels and team, and it connects services and runs a test sort.
Does the agent reply to customers?
No. It sorts and routes requests internally. Replies to customers are a person's or a dedicated sales/support agent's job.
How does it see new requests?
It checks channels on a schedule (default every 30 minutes; 15 for speed). Website forms arrive via forwarded email or a shared sheet — no direct webhook needed.
Do I need paid keys?
No. Gmail, Telegram, and Google Sheets are built-in integrations and free.
Can I connect a real CRM instead of a sheet?
Yes, via API or a custom MCP (HubSpot, Pipedrive, amoCRM) after approval. Out of the box the CRM is Google Sheets, which covers most needs.
How is my data kept safe?
Requests and contacts live only in your sheet, not in agent memory. Each agent is isolated, and you can revoke any service at any time.
What about urgent requests at night?
Routine summaries arrive in your window (08:00–23:00), but a genuinely urgent request may notify outside it — that's the point of escalation.
Use template · Ask a question · Order a done-for-you setup
