Module · Messages
ExpertPress Messages
ExpertPress Messages adds private conversations between a client and a specialist, tied to one booking. Messaging opens at the booking step you choose, closes when the session is over, and is protected by checks that stop contact details, off-platform payment and insults from being sent. The site team gets a moderation queue for safety reports, a support inbox, and a journal of every time staff read a private conversation.
Key capabilities
- Booking conversations. One conversation per booking, opened after payment (default), after the specialist confirms, or as soon as the request is sent. It closes when the session is completed (optionally some hours later), when the booking is cancelled or refunded, and on a complaint.
- Messages in the personal account and the specialist cabinet. An inbox with unread counts, an "Unread" filter, a short conversation preview on the booking page, and new messages that appear without reloading the page.
- Anti-bypass checks. Detects phone numbers, email addresses, messenger handles, card numbers, IBANs, payment phrases and links. For each category and each side (client or specialist) you choose: off, record only, warn, or reject. Meeting links on your allowed domains always pass.
- Insults and threats filter. Messages that contain words from your insults and threats lists are refused.
- Reports and blocks. Clients and specialists can report a message or the other person, and block the other party. Reports go to a staff queue with deadlines, decisions (warning, hide messages, restrict sending) and a full decision log.
- Complaint team chats. When a complaint about a session is filed, each side gets its own conversation with the site team.
- Support requests. Specialists can write to the team (question, bug, review dispute, safety); clients can contact the team about safety. Staff answer from the admin.
- Optional attachments. Images and PDFs (or other types you allow), stored in a private folder that is not reachable from the web.
- Email about unread messages. One email after a short delay, without the message text unless you turn it on. Each person can turn these emails off.
- Staff digest emails. A short email to the team when someone tries to share contacts, without the message text.
- Read journal and retention. Every staff view of a private conversation is logged. Old conversations, journals and closed support requests can be deleted automatically after a period you set.
- Reply templates. Up to 10 personal templates per person that fill the message box (shown when the theme provides the template editor).
Requirements
- ExpertPress core plugin (the main plugin file declares
Requires Plugins: expertpress). If the installed core is too old, the module turns itself off and shows "ExpertPress Messages is turned off: it needs ExpertPress core with shared cabinet navigation support. Update ExpertPress." - WordPress 6.0 or later, PHP 7.4 or later.
- Database tables on the InnoDB engine (the module creates its own tables on activation and upgrades them automatically).
- The PHP
mbstringextension is recommended. Without it the admin shows a warning and phone detection uses a simpler rule set. - For attachments only: a writable folder outside the public web root. By default the module uses a folder named
expertpress-messages-privatenext to (one level above) the WordPress site folder. If that is not possible, your developer must point the module to another private folder with theexpertpress_messages_attachment_storage_dirfilter. The module never stores attachments underuploads/. - No third-party accounts or service keys are needed. Phone number detection uses an embedded copy of the open-source libphonenumber library (Apache License 2.0); it runs on your server and calls nothing outside.
Before anyone can send a message
After activation, messaging stays closed until a staff member fills in the Insults and Threats word lists under ExpertPress → Messages → Safety → Safety settings. Until then, the "Getting started" checklist shows "Nobody can send a message yet. Add the words to refuse for insults and threats in the safety settings." See Safety settings.
The anti-bypass checks are installed but all set to Off. Choose the modes you want on the Anti-bypass tab.
What changes for each audience
Clients
- A Messages (Повідомлення) item in the personal account (default address
/account/messages/) with the list of conversations and each conversation in full. - A Messages block on the booking page with the latest messages and a Full conversation link. Before messaging opens, the booking explains when it will open (for example "Messaging opens after the booking is paid and covers only this consultation.").
- My reports (Мої скарги) and Blocked users (Заблоковані користувачі) items in the account, and Safety support (Безпека — підтримка) to contact the team about safety.
- When a complaint is open, a separate conversation "With the brand team".
- In account settings, Email notifications for new messages can be turned off; each unread-message email also carries a one-click link to turn them off.
Specialists
- A Messages item in the specialist cabinet (default address
/specialist/messages/), the same booking-page block, and the same report and block tools. - Support (Підтримка) in the cabinet for questions, bug reports, review disputes and safety requests.
See Using messages for the full client and specialist experience.
Site team
- ExpertPress → Messages in the admin app (modules group), with the tabs Conversations, Safety, Support requests, View journal and, for managers and administrators, the settings tabs Rules & access, Limits, Anti-bypass and Letters & storage. The menu item shows how many conversations wait for review.
- A Message safety link and counter in the moderation hub, and "Safety reports awaiting a decision" in the operator task list.
- The team chats of a complaint appear in the complaint case.
- On the Video calls settings, a meeting link entered by a specialist is accepted only if its domain is on the Allowed meeting domains list of this module. See Allowed meeting domains.
- Three retention rows (message history, administrator reading history, closed support history) and two more (resolved safety reports, automatic rule violations) appear under Data retention.
Who can open what is described in Settings and admin screens.
Privacy and data
Nothing is sent to external services. All checks run on your server. Emails go out through your site's normal WordPress mail setup.
Stored in your site database:
- conversations, messages and read positions;
- attachment records (the files themselves are in the private folder described above);
- anti-bypass hits: who sent the message, the category, the rule and the matched fragment (for example the phone number that was detected);
- safety reports with their details, decisions, public replies, internal notes, blocks between users and sending restrictions, and a log of every safety action, including when staff opened the original evidence;
- support requests and their messages;
- the staff view journal: who opened which conversation and when;
- personal reply templates (in the user's profile data).
Emails. The unread-message email contains the sender's name, the service, the booking number and a link. The message text is included only if you turn on Include the message text in the email. Staff digest emails never contain the message text.
Retention. By default conversations, the view journal, safety reports and rule hits are kept indefinitely; closed support requests are deleted 730 days after closing. Evidence tied to a complaint, an open report or an active sanction is kept even when its period has passed. Periods are set on the module tabs or, when your core version provides it, under Data retention.
Closed accounts. When an account is closed and its data is erased, the person's name is removed from queued message emails and their reply templates are deleted. The conversations themselves stay, so the other party keeps the history.
Uninstall. Deleting the plugin keeps all conversation data unless Delete conversation tables, admin view log, violations, and module outbox rows when the plugin is deleted is turned on. With it on, the module removes its tables, settings and private attachment files; WordPress user accounts are never deleted.