Setting up a team alert usually means a settings page, a sound library, a list of email addresses and a webhook field in some other tool, all open in different tabs. With Vybit connected to your AI assistant, you describe the alert once in plain words and the assistant does the clicking for you.
What you will hear
A bell on every phone on your team, the moment something needs a person. In our test we asked for a front desk bell: a vybit called "Front desk bell" with a receptionist's bell ringing eight times and the message "Someone needs help at the front desk." Once it existed, the assistant fired a test from the chat, and then we fired it again from its trigger URL the way a webhook would. Both rang the same bell. You will pick your own sound, of course: a cash register for sales, a ship's bell for a new lead, something unmistakable for "the site is down."
Step 1: connect Vybit to your assistant (once)
Vybit runs a hosted MCP server at https://api.vybit.net/v1/mcp. MCP is the standard way AI assistants connect to outside tools. You add it once, sign in with your Vybit account, and from then on any chat can manage your vybits.
Claude (claude.ai or the Claude desktop app), Free, Pro and Max plans
- In any chat, click the + button, choose Add connector, then Add custom connector. (You can also get there from Customize, then Connectors.)
- Name it
Vybit, enter the URLhttps://api.vybit.net/v1/mcpand click Continue. - Leave the default sign-in settings as they are and click Add.
- Sign in to Vybit when asked and click Allow.
- The first time Claude uses each Vybit tool, such as creating or sending a vybit, it asks you first. Approve it, or choose Always allow for the tools you are comfortable with.
Prefer to watch? Here is the whole Claude setup in four minutes, from adding the connector to hearing the first test vybit.
If a later chat does not seem to know about Vybit, open the + menu, then Connectors, and make sure Vybit is switched on.
On Claude Team and Enterprise, an owner adds it once under Organization settings, Connectors, Add, Custom, and each member then clicks Connect on it.
ChatGPT (chatgpt.com on the web), Plus, Pro, Business, Enterprise and Education plans
- Open Plugins at chatgpt.com/plugins.
- Click Add, then Add custom MCP server.
- Name it
Vybit, enter the Server URLhttps://api.vybit.net/v1/mcpand leave Authentication set to OAuth. - Check I understand and want to continue, then click Create as a plugin.
- Sign in to Vybit when asked and approve access.
- In a new chat, type @ and select Vybit.
On Business, Enterprise and Education workspaces, an admin may need to add the plugin or give you permission to add it.
ChatGPT asks you to confirm each action that changes something, such as creating a vybit or sending one. That is a good habit: read what it is about to do, then approve.
The full setup for each assistant also lives on our AI assistants page.
Step 2: copy this prompt
Paste this into a new chat, then change the parts in brackets.
Use my Vybit connector to set up a team alert.
1. Create a vybit called "[Front desk bell]" that is private, with the
default message "[Someone needs help at the front desk]".
2. Search the Vybit sounds for "[bell]" and show me the three best
matches with their play links. Use the one I pick.
3. Invite these teammates to subscribe by email:
[alex@example.com, sam@example.com, jordan@example.com]
4. Give me the vybit's trigger URL (https://vybit.net/trigger/ followed
by its trigger key) so I can paste it into [my help desk / store /
monitoring tool] as an outgoing webhook.
5. Send one test vybit with the message "Test: if you heard this, the
alert works" so I can check the sound on my phone.
Each teammate gets an email invitation, signs in to Vybit (a free account is all they need) and accepts. From then on, every time the vybit fires, all of you hear it, on every device where you have Vybit.
Want it to ring on a schedule instead of from a webhook? Say so: "Make a vybit called Stand-up with a gong sound, on a schedule that rings the team at 9:55 on weekdays, Denver time." Use the word schedule for anything that repeats; Vybit's reminders are meant for one-off dates, like "Oct 20 at 7 PM, put the recycling out."
Step 3 (optional): wire it to the tool that knows when it should ring
Most tools that can send an outgoing webhook can fire a vybit. Paste the trigger URL into that tool's webhook or notification settings. A POST with a JSON body like {"message": "Ticket 4821: printer on fire"} replaces the default message for that one alert, so your team knows what happened before they pick up the phone.
If your assistant also has Zapier, Make or n8n connected, you can ask it to build that part too: "Create a Zap that sends my Front desk bell vybit whenever a new ticket is tagged urgent." Vybit is an official app on Zapier, Make and IFTTT, and there is a Vybit community node for n8n, so you can pick your vybit from a list in any of them.
How counting works
One notification is one vybit reaching one person, on all of their devices, and that includes you. So an alert that rings you and 8 teammates uses 9 notifications. Subscribers are free and unlimited, and nobody needs a seat to listen.
For a front desk crew of 9 with about 10 alerts a day, that is 9 x 10 x 30 = 2,700 notifications a month. A support team of 24 with about 20 alerts a day uses about 14,400.
Which plan fits
- Free covers a small team with a few alerts a day: 1,500 notifications a month and 10 vybits.
- Pro fits the crew of 9 above: 3,000 notifications a month, 20 vybits and 3 manager seats.
- Team fits the support team of 24: 15,000 notifications a month, 50 vybits and 20 manager seats.
Manager seats are only for people who help you run the account (your vybits, sounds and logs). Everyone who just needs to hear the alert subscribes for free. The pricing page has the full comparison, and if you need more than Business offers, write to plans@vybit.net.
Your assistant can also tell you where you stand at any time. Ask it "How many Vybit notifications have I used this month?" and it will read your meter.
Originally published on Signals, the Vybit blog.
