Bot not responding

Symptom: You send a message on Telegram and get no response.

• Check the Command Portal at app.agente.systems — is your agent showing as online?
• Verify your channel connection is still active in Settings → Channels
• Try sending a simple message like "hello" — complex messages sometimes confuse routing
• If the bot is online but not responding, check if you hit your usage limit for the billing period
• Last resort: disconnect and reconnect the channel

Wrong routing

Symptom: Your question goes to the wrong seat (e.g., a legal question gets answered by the CFO).

• Be more specific in your request — "review this contract for risk" routes better than "look at this"
• You can explicitly request a seat: "Ask the CLO to review this contract"
• If routing is consistently wrong, your COO may need a context update — tell it about the correction
• Routing improves with usage — the COO learns your patterns

Stale or incorrect memory

Symptom: The C-Suite references outdated information or gets facts wrong.

• Correct it directly: "Actually, Jenny's title is VP of Operations, not Partner"
• The C-Suite updates its memory from corrections in conversation
• For bulk corrections, use the Command Portal → Memory → View/Edit
• You can also say "forget X" or "update X to Y" for targeted corrections

Login problems

Symptom: Can't log into the Command Portal.

• Make sure you're using the correct email — login is tied to your account email
• Check spam folder for the magic link email
• Clear browser cookies and try again
• If you've lost access to your email, contact support from your registered channel

Channel disconnected

Symptom: Your Telegram bot stopped responding.

• Make sure the bot hasn't been blocked. Try sending /start to the bot
• Check if the bot shows as online in the Command Portal
• Try sending a simple message like "hello" to reset the session
• If still unresponsive, disconnect and reconnect from Settings → Channels

Email integration not working

Symptom: COO can't read emails or calendar events.

• Check if your OAuth token has expired — reconnect in Settings → Integrations
• Verify the permissions granted include read access to email and calendar
• For Microsoft 365: Make sure your admin hasn't revoked app permissions
• For Gmail: Check that Less Secure Apps isn't blocking the connection

Still stuck?

If none of the above fixes your issue:

• Ask your COO to run a diagnostic: "Run a health check"
• Check the FAQ for your specific question
• Message support through the Command Portal