Telegram
Telegram is where you talk to Pepper: briefs, follow-ups, questions, voice notes, and the buttons you tap to say yes. You do this through a bot you make for Pepper. Voice notes need speech-to-text set up on the Mac (see Install Pepper), unless you chose to send them to OpenAI instead.
This is separate from your Telegram chats with other people. If you want Pepper to read those, add Telegram to Beeper, the app that brings your chat apps to Pepper.
- In Telegram, message @BotFather, Telegram's own bot for making bots, send
/newbot, and pick a name. It answers with a token, the secret that lets Pepper use the bot. - Message @userinfobot to get your numeric user ID.
- Put both in
.env, Pepper's settings file:TELEGRAM_BOT_TOKEN=… TELEGRAM_OWNER_ID=… - Restart Pepper and send the bot
/status.
npm run setup telegram does steps 2 to 4 for you: it learns your ID from your first message to the bot.
Messages from any other account are ignored, and forwarded messages are never treated as coming from you.
If Telegram starts refusing Pepper's messages, the Connections page on the dashboard shows the problem, because
Pepper notes whether each text message it sends you got through. A rejected token (401 Unauthorized) shows as
needs you, because only you can make a new one.
If the token leaks, or BotFather revokes it: message @BotFather, send /token, pick the bot, put the new token
in .env, and restart Pepper. Your chat history with the bot stays.
Tactiq meetings
If you record meetings with Tactiq, Pepper can read the transcripts. Once you confirm it, a promise you make on a call shows up next to the ones you make in chat.
Phone line
Pepper can answer calls through a spare Android phone plugged into the Mac. The Android bridge is that phone plus a small call server on the Mac. The phone signs in to the server, and Pepper talks…