Enterprise · Partners
Partner & vendor agent
B2B status and FAQs for people who are not customers and not employees — from a pack you would be willing to show a vendor.
B2B status and FAQs for people who are not customers and not employees — from a pack you would be willing to show a vendor.
Partners get angry when they hit the consumer support bot and hear “where is my hoodie.” They also should not see employee IT runbooks. This is a third audience.
Customer-facing mode, partner-safe docs and tables (price lists they are allowed to see, shipment status on their POs, integration how-tos). Escalation to a channel manager, not to generic L1 support, when the contract is in play.
B2B
Not consumer support
Different pack, different owners
PO
Their records
Status on rows they are allowed to see
Manager
Contract escalations
Channel owner, not L1 macros
Traditional tools
A partner PDF from 2022 plus a consumer chatbot plus a BD email that takes three days.
With Maicos
A partner pack, tables scoped to that partner’s IDs, and a human path to the channel manager.
A portal with a conversation, still permissioned like a portal.
Integration guides, program rules, MDF policy. If you would not put it on a partner portal, the agent should not say it.
POs and tickets filtered by partner ID. A reseller should not see another reseller’s pipeline.
Contract, pricing exception, or co-sell — those go to a named human, not the consumer refund flow.
The agent cannot magically know your NDA. Keep confidential deal terms out of the public partner pack.
Audience, identity, pack, escalation. In that order.
A code, a domain, a login you already have. Anonymous “partner” chat is how list prices leak.
Row-level scope is the product. If you cannot filter, do not connect the table.
Program rules, SLAs you already published. No verbal discounts.
The channel manager owns paper. The agent owns status and how-to.
Reseller A should only see reseller A.
Partner authenticates or enters a partner code you trust
Unverified people get the public brochure, not PO status.
Agent looks up PO 77 in a filtered table
Match on partner_id. Miss → “I don’t see that PO” plus the channel owner, not a guess.
How-to questions use the partner integration doc
Cite the section. If the doc is silent, escalate.
They ask for extra discount
No. Open a task for the channel manager with the transcript.
Partner agents fail as consumer bots with a friendlier greeting. They succeed as portals that can talk, with the same access control as the portal.
If the answer would require a signature, it is a human. If it is “what is the status of my PO,” it is a filtered table.
Support Agent
Live · customer-facing
The same apps you already work in — not a second chatbot that needs uploads.
Useful agents have a job description. These limits keep this page honest — and help you pick a different agent when you need one.
How people use this every day.
Filtered table, honest misses, human on disputes.
Cite the partner doc. Out-of-doc questions become tickets to partner engineering, not consumer L1.
MDF, deal registration — quote the PDF. Exceptions to BD.
You may need two packs. A vendor asking when you will pay them is not a reseller asking when you will ship.
A customer-facing Maicos agent for vendors or resellers: FAQs from a partner pack, status from tables scoped to that partner, escalations to a channel owner — not the consumer support bot.
Filter tables by partner identity. If you cannot, do not connect the table. Identity is a prerequisite, not a nice-to-have.
No. Collect the request and route it to a human. Verbal discounts from a model are how you get two partners with two secret prices and no paper.
It can sit in front of partner docs and POs. If you already run a PRM, integrate; do not fork certifications and deal registration.
Public can see brochure docs. Status and price lists need authentication or an equivalent partner code you trust.
Start free — Workspace, Create, Automate, and Integrations built for AI from day one.
No credit card required · Free during beta