Channels and communication

A channel is a way Player One reaches you and you reach Player One: Telegram, WhatsApp, Slack, Discord, your email, and the web app itself. Behind every one of them is the same assistant, with the same memory of your business and the same access to your files and tools, so a question you ask from the school gates is answered by the colleague you were talking to in the browser that morning.

The channels

Telegram, WhatsApp, Slack and email have a guided setup. Say "connect my email" and your assistant does the work with you, stopping at the one step only you can do: scanning a code, approving the app in your workspace, or fetching an app password. It will not take a password or a token typed into the conversation; those go into a secure field instead.

Discord and others are supported without a guided setup of their own, so connecting one is more question and answer and less walkthrough.

Which agent answers on a connection is yours to choose. A bot you hand to customers can be answered by the support agent you built for them rather than by your own assistant; ask your assistant to set that up when you connect it.

When Player One needs you

Most of the work that generates messages happens while you are elsewhere: a scheduled task at six in the morning, a flow paused for your approval, a job that hit a decision nobody delegated. When something needs an answer, Player One asks. When it only needs you to know, it tells you.

Every question and alert carries a level: Urgent, Normal or Quiet. You decide which channels each level uses, so Urgent might reach Telegram and Slack while Quiet stays out of your evening. Whatever you pick, the bell inside Player One is included as well, so nothing exists only on one app and there is always one place with the whole record.

Answer wherever the message found you. A "yes, go ahead" typed into Telegram unblocks the flow that asked, exactly as answering in the bell would, and the chat that asked gets your answer with a line saying where you gave it. A question left unanswered expires after a day unless it set its own deadline, and the chat that asked is told. The one thing to watch is several questions waiting on the same app at once: use that app's own reply feature on the one you mean, because Player One will not guess.

When a message starts the work

The traffic runs the other way too. An email landing in your support inbox or a message arriving on Telegram can start a process rather than just a conversation, which is what flows are for.

The Messaging page

Admin > Messaging (/admin/channels), in the Communications group, is one card for every messaging and email connection, with its live state: Connected, Idle, Error, Not set up or Off. Refresh re-checks all of them at once. Set up hands an unconnected channel to the assistant to walk with you, and Repair does the same for one that has broken. Each connected account has its own row, so two mailboxes or two Slack workspaces sit side by side, and Disconnect logs out one of them without touching the rest. A connected card also carries Test, which sends you a real message on that channel, for every channel except email.

The Alerts page

Admin > Alerts (/admin/alerts) is where you say what should be sent where. It has three tabs.

• Routing is the three levels and which channels each one uses. The bell is ticked and locked on every level.
• Channels holds the addresses Player One sends to: your Telegram chat, your Slack user, your WhatsApp number. Each can have more than one, labelled so you can tell your personal from your work one, and each has a Test button that sends a real notification and tells you if it failed.
• History is the last fifty things Player One asked you, with what you answered.

Anything still waiting sits in a panel at the top of the page under Waiting for you, whichever tab you are on, so you can clear the backlog in one place.

Contacts

Alerts covers reaching you. Manage > Contacts (/manage/contacts) is everyone else: the address book Player One uses when the work involves other people, with a row per way of reaching each of them and an order of preference among those rows.

Contacts group into named lists, chosen from the pill row under the page title, and each list is its own book. That keeps a guest list for one event separate from your main directory, and lets the same address belong to a person in each. Tags cut across lists, so "everyone tagged speaker" or "everyone tagged admin" is something you can address in one go. A project can be given its own contact lists on its Resources tab, while the contacts inside them stay shared.

Player One does not quietly add strangers to your address book. A message from an unknown sender is still a message; whether that person becomes a contact is your decision.

For the steps, see Connect Telegram, WhatsApp, Slack or email. Talk to it shows what each way in feels like, and Scheduled tasks and watchers covers the unattended work that sends most of these messages.