Setup & Connection
The WhatsApp integration uses a QR code flow — no API keys or developer configuration needed. Setup takes under two minutes.
Open Integration Settings
In your Everia project, go to Settings → Integrations → WhatsApp and click Connect.
Scan the QR code
A QR code is displayed in Everia. Open WhatsApp on your phone → Settings → Linked Devices → Link a Device, then scan the code.
Confirm the connection
Everia shows a confirmation when the scan succeeds and the bot session is established.
Link your project
Send /link to the Everia bot number. If you have multiple projects, choose the one you want this chat to be associated with.
Commands Reference
Send /help to the bot at any time for the full list. Commands follow the same syntax as the Telegram integration.
/create [title]— Create a new ticket in the linked project/status [ticket-id]— Get status, assignee, and sprint for a ticket/assign [ticket-id] [user]— Assign a ticket to a team member by name or email/close [ticket-id]— Mark a ticket as Done/sprint— Active sprint overview — progress, blockers, end date/sprint list— List all sprints with status/search [query]— Search KnowHub and return matching page excerpts/ask [question]— Ask the AI a project question — answers grounded in your data/link— Link this chat to an Everia project/unlink— Remove the project link from this chat/help— Show all available commandsCreating tickets from messages
Forward or quote any WhatsApp message and reply with /create. The quoted message becomes the ticket description automatically.
Voice-to-text input
WhatsApp's voice-to-text feature works with bot commands. Dictate /create Fix the payment timeout on checkout and WhatsApp transcribes it before sending — useful when you can't type.
Notifications
Configure which events send a WhatsApp message. Go to Settings → Integrations → WhatsApp → Notification Settings.
Test run completed
Summary with pass / fail / blocked counts and a link to the full report.
Fail rate exceeded
Alert when test failures exceed a configurable threshold in a run.
Ticket assigned to me
Personal notification when a ticket lands in your queue.
Ticket status changed
Notify the chat when a ticket moves to a new status column.
Sprint started / closed
Announce the start and end of each sprint with a short summary.
Blocker added
Immediate alert when any ticket is marked as Blocked.
Group Chat Support
The Everia bot can be added to a WhatsApp group so the whole team can use commands and receive notifications in a shared channel.
Add the bot to a group
Save the Everia bot number as a contact, then add it to an existing or new WhatsApp group.
Link the group to a project
Any group member sends /link to associate the group with an Everia project.
Individual account linking
Each team member sends /auth to the bot in a personal chat to link their WhatsApp number to their Everia account. This ensures tickets they create are attributed to them correctly.
Configure group notifications
Notification settings apply to the group. Choose events that are relevant for the whole team — avoid noisy per-user notifications in a shared group.
- Actions taken in the group (e.g. /assign) are attributed to the individual's linked Everia account, not the group.
- Group chats can only be linked to one project. Use separate groups for separate projects.
- The bot ignores messages that are not commands — normal team conversation is not processed.
Troubleshooting
Bot stops responding after a few days
This is a WhatsApp Linked Devices session expiry. Re-scan the QR code in Settings → Integrations → WhatsApp. Sessions expire after ~14 days of phone inactivity.
QR code expires before I can scan it
The QR code refreshes every 60 seconds. Click Refresh QR in the Everia integration panel if it expires, then scan the new one quickly.
/link returns 'no projects found'
Make sure your WhatsApp number is linked to an Everia account with at least Member access to a project. Run /auth first to link your personal number.
Notifications arrive in the wrong chat
Check Settings → Integrations → WhatsApp to confirm which chat is linked for notifications. Unlink the wrong one and re-link the correct chat.
Ticket created without an assignee
/create does not auto-assign. Use /assign [ticket-id] [name] immediately after, or set a default assignee in project settings.