Counting the no-shows
Sarah Chen, sales operations manager at Acme Ltd, asked how many meetings were no-shows this week. Memtro read the week's meetings with status NoShow, named each assigned rep from the users list and counted them per rep.
Who booked with our reps this week, and who did not show up?
Chili Piper connects Memtro to your sales scheduling and routing. It reads meetings in a window of up to a week, with status, guests and the assigned rep, the Distro, Handoff and Concierge routers and which are active, and users and workspaces, so a rep's id gets a name. When asked, and once an administrator has granted the action by name, it can book a meeting, which sends the guest invites at once, cancel one permanently, mark a no-show or attendance, which may update the CRM, set a rep Available or Away, switch Distro routers and invite users.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Chili Piper tool, reads what it needs, and answers with the source cited.
These tools change something in Chili Piper. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
Once Chili Piper is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
How many Chili Piper meetings were no-shows this week?
Which meetings is Dan Fletcher assigned next week?
Which Distro routers are active?
Has jane@bigco.com booked a meeting this week?
Mark my 2pm with Globex as a no-show
Sarah Chen, sales operations manager at Acme Ltd, asked how many meetings were no-shows this week. Memtro read the week's meetings with status NoShow, named each assigned rep from the users list and counted them per rep.
Tom Reilly, account executive at Northwind, told Memtro his 2pm guest from Globex never joined. Memtro marked the Chili Piper meeting as a no-show, which updated the meeting outcome on the CRM record and set off the no-show follow-up the team had configured.
The teams that lean on Chili Piper most, a question each of them asks, and what they connect beside it.
A record in Chili Piper is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
In Chili Piper, open Admin Center → API Keys, or Command Center → Integrations → Credentials → API Access Tokens. Creating a key needs an admin.
Create a key named Memtro with Read and Ping permission on meetings, workspaces, users, routers and meeting types. For actions add only those you want: scheduling-links.schedule, meeting.modify, user.modify, distro.modify, user.invite. Copy it, as it is shown once.
In Memtro, open Connections → Chili Piper and paste it into API key.
Ask your first question: how many Chili Piper meetings were no-shows this week?
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Chili Piper tools are the same everywhere.
Only when you ask, and only what it has been granted: book a meeting for a host on their personal meeting type (sends calendar invites to the guest); cancel a meeting (permanent, may email attendees); mark a meeting as a no-show (may update the CRM and run workflows); mark a meeting as attended (may update the CRM and run workflows); set a user Available or Away for live routing; turn a Distro router on so it routes records; turn a Distro router off so it stops routing records; invite a user to Chili Piper (emails them only if asked). Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.
API key. In Chili Piper, open Admin Center → API Keys, or Command Center → Integrations → Credentials → API Access Tokens. Creating a key needs an admin.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time