You need three things and only one of them is the assistant. An app registered with Slack, Teams or Google Chat and reviewed by them; a way to turn an incoming workspace id into the right customer with the right credentials, which must never be wrong once; and per-customer access to your own product, so the assistant answers as that customer rather than as you. Meetext provides the second and third and carries the message both ways, so what you build is the assistant. Your model, your prompt and your name on the bot, with nothing identifying Meetext to the person asking.

If you are asking because every enterprise customer needs weeks of engineering before they can use what they bought, a hire will solve it for the next two or three customers and then you will need another one. The work is roughly the same each time: the same OAuth flow, the same security questionnaire, the same validation, the same upgrade, against a different tenant. That part is a software problem. Hire for the judgement work, which is understanding what a customer actually needs, and make the repetition somebody else's infrastructure.

No. An OpenAPI document works, and so does a repository. Meetext scans FastAPI, Flask, Django, Next.js and Express for routes and service functions. Whichever you connect normalises into the same internal capability format, so every destination behaves identically.

Capability results pass through the hosted endpoint in memory to reach the destination. They are not stored. Execution is audited by argument name only and never by value, so Meetext records that a search happened and not what was searched for. Credentials live in a secret manager under a name scoped to a single customer environment and are never shared between two customers.

Slack, Microsoft 365, Google Workspace, Salesforce, ServiceNow, Atlassian and HubSpot. All seven are in preview: the adapters are complete and covered end to end against provider simulators, and none has yet run against a real provider account. Meetext will not describe a destination as available until every part of the deployment lifecycle has actually run against the real provider, and a test refuses the claim without dated evidence.

One customer, one product, one destination. It counts while it is installed. Disconnected environments do not count, and calling your capabilities more often never changes the bill.