Module · Messages
Messages: settings and admin screens
Where: ExpertPress → Messages (Повідомлення), in the modules group of the ExpertPress admin app.
The Messages screen has these tabs: Conversations (Листування), Safety (Безпека), Support requests (Звернення), View journal (Журнал переглядів), and the settings tabs Rules & access (Правила та доступ), Limits (Ліміти), Anti-bypass (Контроль обходу платформи) and Letters & storage (Листи та зберігання). Safety settings (Налаштування безпеки) opens from a button on the Safety tab.
Each settings tab is one form with one Save button (on Safety settings: Save settings). After saving you return to the same tab with a green or red message.
Who can use these screens
Access follows the ExpertPress team roles described in Roles and access.
| Screen | Administrator | Manager | Moderator | Accountant |
|---|---|---|---|---|
| Conversations — list and reading | all conversations | all conversations | only bookings with a complaint (unless Read scope allows all) | no |
| Mark a flagged conversation Verified | yes | yes | yes | no |
| Reply as the team in complaint chats | when Reply from admin is on | when Reply from admin is on | no | no |
| Safety queue — reports and decisions | yes | yes | yes | no |
| Remove pair blocks | yes | yes | no | no |
| Support requests | yes | yes | yes | no |
| View journal | yes | yes | yes | no |
| Rules & access, Limits, Anti-bypass, Letters & storage, Safety settings | yes | yes | no | no |
None of the options on these tabs is administrator-only: a Manager can change all of them. Accountants do not see private conversations; they see the team chats of money disputes inside the complaint case.
Rules & access
Where: ExpertPress → Messages → Rules & access. Page title: Message rules & access (Правила переписки та доступ).
Open on
- Where: Rules & access → When the conversation opens (Коли переписка відкривається)
- What it does: Sets the booking step at which the client and the specialist can start writing. Before that, the booking and the conversation show when messaging will open.
- Default: After payment (default).
- Values / limits: After payment (default) (Після оплати), After specialist confirmation (Після підтвердження спеціалістом), When the booking is created (Коли запис створено).
- When to change it: choose confirmation if specialists need to ask questions before the client pays; choose creation if specialists decide whether to confirm based on a short exchange; keep payment to reduce attempts to agree on payment outside the site.
- Related: The booking flow, Anti-bypass
Hours open after completed
- Where: same section (Скільки годин листування відкрите після консультації)
- What it does: How long the conversation stays open after the session is marked completed.
- Default: 0 — closes as soon as the session is marked completed.
- Values / limits: 0–8760 hours.
- When to change it: 24–72 hours if specialists send materials or follow-up notes after a session.
Keep the conversation open when the booking is canceled
- Where: same section, Cancel row
- What it does: When on, a cancelled booking does not close its conversation.
- Default: off (a cancelled booking closes the conversation).
- Values / limits: on / off.
- When to change it: turn on if clients and specialists usually agree on a new booking after a cancellation.
Close the client↔specialist chat as soon as a complaint is filed
- Where: Rules & access → Complaints (Скарги), Close parties on complaint
- What it does: When a complaint about the session is filed, closes the conversation between the client and the specialist. The separate conversations of each side with the team stay open.
- Default: on.
- Values / limits: on / off.
- When to change it: turn off if you want the parties to keep talking while the team reviews the complaint; then choose the outcomes below.
- Related: Complaints
Outcomes that close the parties’ chat
- Where: same section
- What it does: Used only when the option above is off. When the complaint is decided with one of the ticked outcomes, the client–specialist conversation closes.
- Default: Full refund.
- Values / limits: the decision outcomes of the core complaint process, for example No refund, Payout released to the specialist, Full refund, Partial refund, Noted, no money moved, Withdrawn. The list comes from the core plugin.
- When to change it: add Partial refund if any money returned to the client should end the conversation.
Read scope
- Where: Rules & access → Admin access (Доступ адміна)
- What it does: Decides which conversations moderators may open on the Conversations tab.
- Default: Complaint only for moderators/accountants; manager sees all (default) — moderators see only conversations of bookings with a complaint; managers and administrators see all.
- Values / limits: the default above, or Everyone with message read access sees all conversations.
- When to change it: widen it only if moderators must actively check conversations for anti-bypass hits without a complaint, and your privacy notice allows it.
Reply from admin
- Where: same section
- What it does: Allow team replies from the Messages screen (shown as the team, not the staff name). When on, managers and administrators see a Reply as the team form in an open complaint team chat. The party sees the team name, not the staff member's.
- Default: off.
- Values / limits: on / off. Replies are possible only in complaint team chats, never in the client–specialist conversation ("Operators do not write in the conversation.").
- When to change it: turn on when your team handles complaints by writing to each side.
Conversations per page
- Where: same section
- What it does: Page size of the Conversations list and the View journal.
- Default: 20.
- Values / limits: 1–200.
Keep journal for (days)
- Where: same section, View journal row
- What it does: How long rows of the staff view journal are kept. The journal itself cannot be turned off: "Every admin view is logged. Without a journal row the conversation is not shown."
- Default: 0 — keep forever.
- Values / limits: 0–36500 days. When your core plugin manages retention centrally, the field is replaced by the current period (for example "Keep indefinitely") and a Data retention link; the period is then set there under Administrator reading history.
- When to change it: set 365 days or the period your privacy policy names for access logs.
- Related: Data retention
Limits
Where: ExpertPress → Messages → Limits. Page title: Message limits & addresses (Ліміти повідомлень і адреси).
Max message length
- Where: Limits → Sending limits (Ліміти надсилання)
- What it does: The maximum number of characters in one message. Also limits reply templates.
- Default: 2000.
- Values / limits: 100–20000.
- When to change it: raise it to 5000 if specialists send long preparation instructions.
Messages per window
- Where: same section
- What it does: How many messages one person may send within the rate window.
- Default: 20.
- Values / limits: 1–1000.
Rate window (seconds)
- Where: same section
- What it does: The time window for the limit above.
- Default: 60 seconds.
- Values / limits: 10–3600.
- When to change it: lower the number of messages (for example 10 per 60 seconds) if you see spam bursts.
Allow attachments in conversations
- Where: Limits → Attachments (Вкладення)
- What it does: Lets the client and the specialist attach one file to a message. Files are kept in a private folder outside the public web root and are downloaded only through a checked link by the participants and the team.
- Default: off.
- Values / limits: on / off. Turning it on fails with an explanation when the private folder cannot be created or is reachable from the web ("Private attachment storage is not available…"); see Requirements.
- When to change it: turn on if specialists need to receive photos, charts or documents before a session.
Max file size (KB)
- Where: same section
- What it does: The largest file a person can attach.
- Default: 2048 KB (2 MB).
- Values / limits: 50–20480 KB. The screen also shows the server's own upload limit; a larger value is capped at it.
Allowed MIME types
- Where: same section
- What it does: The file types people may attach, separated by commas.
- Default:
image/jpeg, image/png, image/webp, application/pdf. - Values / limits: MIME types in the form
type/subtype. Invalid entries are dropped; an empty list goes back to the default. - When to change it: remove
application/pdfto allow only pictures; addimage/heicif many clients send photos from iPhones.
Inbox conversations per page
- Where: Limits → Inbox & polling (Вхідні повідомлення та оновлення)
- What it does: Page size of the Messages list in the client account and the specialist cabinet.
- Default: 0 — all conversations on one page.
- Values / limits: 0–200.
Preview length
- Where: same section
- What it does: How many characters of the last message the inbox shows as a preview.
- Default: 120.
- Values / limits: 20–500.
Poll interval (seconds)
- Where: same section
- What it does: How often an open conversation asks the server for new messages.
- Default: 15.
- Values / limits: 5–300.
- When to change it: raise it to 30–60 on a busy site or slow hosting to reduce server load.
Client messages path
- Where: Limits → Cabinet addresses (Адреси кабінету)
- What it does: The address of the client's message list, without the leading slash.
- Default:
account/messages. - Values / limits: lowercase letters, digits,
-,_and/, up to 80 characters; the first part cannot be a WordPress system folder. It must differ from the specialist path and must not be taken by another account screen ("That client messages path is reserved for another screen."). Saving a new path refreshes the site addresses, and the default path then redirects to the new one. - When to change it: match a translated account address, for example
kabinet/povidomlennia.
Specialist messages path
- Where: same section
- What it does: The address of the specialist's message list.
- Default:
specialist/messages. - Values / limits: same rules as the client path.
Active requests per specialist
- Where: Limits → Support requests (Звернення)
- What it does: How many open or answered support requests one author may have at a time.
- Default: 5.
- Values / limits: 1–100.
New requests per day
- Where: same section
- What it does: How many new support requests one author may create per day.
- Default: 10.
- Values / limits: 1–500.
Author reopen window (days)
- Where: same section
- What it does: After the team closes a request, the author may reply to reopen it within this many days.
- Default: 30.
- Values / limits: 0–3650.
Closed support retention (days)
- Where: same section
- What it does: Closed support requests and their messages are deleted this many days after closing. Open requests and anything tied to a complaint are kept.
- Default: 730.
- Values / limits: 0–3650 (0 keeps closed requests). When the core plugin manages retention centrally, the field is replaced by a link to Data retention, row Closed support history.
- Related: Data retention
Support mailbox
- Where: same section
- What it does: Receives an email for each new support request and each author reply.
- Default: empty — the site administrator's email (WordPress → Settings → General) is used.
- Values / limits: one valid email address.
- When to change it: use a shared team inbox such as
support@your-site.
Anti-bypass
Where: ExpertPress → Messages → Anti-bypass. Page title: Message anti-bypass (Контроль обходу платформи у повідомленнях).
The checks look for ways to move the conversation or the payment off your site. They recognise common disguises such as numbers written as words, spaced-out digits and messenger nicknames. Built-in word lists exist for English, Ukrainian and Russian; English is always used, plus the lists for the languages installed on your site. The checks apply to conversations between clients and specialists, not to support requests.
Modes
- Where: Anti-bypass → Modes (Режими), a table with one row per category and a column for Client and Specialist
- What it does: For each category and side, decides what happens to a matching message:
- Off (Вимкнено) — no check.
- Observe (journal only) (Спостереження) — the message is sent and the hit is recorded.
- Warn (Попередження) — the sender sees the warning text and can edit or Send anyway.
- Reject (Відхилення) — the message is not sent. When a message matches several categories, the strictest mode wins.
- Categories:
- Contacts (phone, email, messengers) — phone numbers, email addresses, Telegram, Viber, WhatsApp, Instagram, Facebook and TikTok handles and links.
- Off-platform payment — card numbers, IBANs, payment phrases and your Stop phrases.
- Links (except meeting domains) — any web link whose domain is not on the allowed meeting domains list.
- Default: Off for every category and side.
- When to change it: a common start is Warn for Contacts and Links and Reject for Off-platform payment, for both sides; use Observe for a few weeks first if you want to see how often it triggers.
- Related: Write violations to the journal
Allowed meeting domains
- Where: Anti-bypass → Allowed meeting domains (Дозволені домени зустрічей)
- What it does: Links to these domains (and their subdomains) are never treated as a link or contact hit, so a specialist can send a meeting link. The same list also limits the meeting link a specialist enters for a session under Video calls: a link on another domain is refused.
- Default:
meet.google.com,zoom.us,zoom.com,teams.microsoft.com,teams.live.com,meet.jit.si,whereby.com. - Values / limits: one domain per line. An empty list means no meeting link domain is allowed at all.
- When to change it: add the domain of the meeting service your specialists use (for example
us02web.zoom.usis already covered byzoom.us; addskype.comonly if you accept Skype).
Stop phrases
- Where: Anti-bypass → Stop phrases (Стоп-фрази)
- What it does: Extra phrases that count as Off-platform payment, so they follow that category's mode. Matched case-insensitively after the text is normalised.
- Default: empty.
- Values / limits: one phrase per line; duplicates are removed.
- When to change it: add phrases you see in practice, for example "pay me directly" or a local payment app name.
Blocked keywords
- Where: Anti-bypass → Blocked keywords (Стоп-слова)
- What it does: A message containing one of these words or phrases is always rejected, whatever the category modes are (even Off).
- Default: empty.
- Values / limits: one phrase per line, case-insensitive, matched anywhere in the text.
- When to change it: add the name of a competing platform or a payment service you never allow. Keep it short: a common word here will block normal messages.
Warning text
- Where: Anti-bypass → Texts (Тексти)
- What it does: The text shown when a message hits a Warn rule.
- Default: empty — the built-in text "This message looks like it shares contact details. Edit the message, or send it anyway.", translated into the site language.
- Values / limits: plain text. A custom text is shown as written, in every language.
Reject text
- Where: same section
- What it does: The text shown when a message is rejected by a mode or a blocked keyword.
- Default: empty — the built-in text "This message looks like a payment outside the platform. Edit the message and try again."
- Values / limits: plain text.
- When to change it: if you reject contacts as well as payments, write a neutral text such as "Please keep contacts and payments on the platform."
Write violations to the journal and flag conversations
- Where: same section
- What it does: Records every hit (sender, category, rule, matched fragment) and marks the conversation for review on the Conversations tab (With violations filter and the menu counter). Staff digest emails also depend on this record.
- Default: on.
- Values / limits: on / off. When off, Observe mode has no visible effect.
- When to change it: keep it on. Old hits can be deleted automatically under Data retention, row Automatic rule violations.
Email staff about contact-sharing attempts in chat
- Where: Anti-bypass → Staff digest emails (Зведені листи для команди)
- What it does: Sends one email per conversation per time window to administrators, moderators and managers. The letter states the fact, the categories, the senders and links to moderation and the participant dossier. It never includes the message text.
- Default: on.
- Values / limits: on / off.
- When to change it: turn off if your team checks the Conversations tab daily and does not want email.
Digest window (minutes)
- Where: same section
- What it does: Repeated hits in the same conversation within this window are combined into one email.
- Default: 15.
- Values / limits: 1–1440.
- When to change it: 60 minutes if one persistent user produces too many emails.
Letters & storage
Where: ExpertPress → Messages → Letters & storage. Page title: Message letters & storage (Листи й зберігання повідомлень).
If some private attachment files could not be deleted during cleanup, a warning at the top shows how many are waiting, with a Retry cleanup button that runs one cleanup pass and reports how many files were removed and how many remain.
Send emails about unread messages
- Where: Letters & storage → Letters (Листи)
- What it does: Emails the recipient when a new message stays unread. One email covers the conversation until it is read. Each person can turn these emails off for themselves.
- Default: on.
- Values / limits: on / off. Emails go through the site's WordPress mail setup.
Delay (minutes)
- Where: same section
- What it does: How long to wait after the first unread message before emailing. If the person reads the message in the meantime, no email is sent.
- Default: 10.
- Values / limits: 0–10080 (up to 7 days).
- When to change it: 30–60 minutes if people complain about too many emails during an active conversation.
Batch size
- Where: same section (Листів за один запуск)
- What it does: How many conversations are processed per background run.
- Default: 200.
- Values / limits: 1–1000.
- When to change it: lower it if your mail provider limits how many emails you can send per minute.
Subject
- Where: same section
- What it does: The email subject.
- Default: empty — the built-in "New message", translated into the recipient's language.
- Values / limits: placeholders
{sender},{service},{order},{url},{text}. A text with an unknown placeholder is not saved.
Body
- Where: same section
- What it does: The email text.
- Default: empty — the built-in text: "New message. From: {sender}. {service} #{order}. {url}", each on its own line.
- Values / limits: plain text with the same placeholders. Every email also ends with a "Turn off message emails" link.
- When to change it: add a line such as "Reply on the site — your contacts stay private."
Include the message text in the email (off by default)
- Where: same section
- What it does: Puts the message text into the email (in
{text}, or at the end if the template has no{text}). - Default: off.
- Values / limits: on / off.
- When to change it: keep it off: it sends private content by email and lets people answer outside the site.
Retention (days)
- Where: Letters & storage → Storage (Зберігання)
- What it does: Conversations older than this are deleted in the background, together with their attachments. Complaint evidence is kept.
- Default: 0 — keep forever.
- Values / limits: 0–36500 days. When the core plugin manages retention centrally, the field is replaced by a link to Data retention, row Message history.
- When to change it: set the period from your privacy policy, for example 1095 days (3 years).
- Related: Data retention
Delete conversation tables, admin view log, violations, and module outbox rows when the plugin is deleted
- Where: same section
- What it does: When on, deleting the plugin in WordPress → Plugins also deletes all module data: conversations, messages, attachments and their files, the view journal, violations, safety records, support requests and module settings. User accounts are never deleted. If any file cannot be removed, uninstall stops and keeps the data.
- Default: off — history is kept after uninstall.
- Values / limits: on / off.
- When to change it: turn on only right before you remove the module for good and have exported anything you must keep.
Safety settings
Where: ExpertPress → Messages → Safety → Safety settings button.
These settings control safety reports and the insults and threats filter. Until they are saved, nobody can send a message (and the checklist shows "Nobody can send a message yet…"). All fields are required. The form refuses a save if someone else saved in the meantime; reload and try again. The last 50 changes are listed below the form under Safety journal.
The language-specific fields come in two sets, Ukrainian and Russian. A visitor whose site language is Russian sees the Russian texts; everyone else sees the Ukrainian ones.
Triage hours (1–720)
- What it does: Calendar hours within which the team should take a new report for review. Shown to the reporter and on the public safety contact page.
- Default: not set.
- Values / limits: 1–720. New values apply only to new reports.
- When to change it: 24 hours for a team that checks the queue daily.
Decision business days (1–90)
- What it does: Business days (Monday to Friday in the site time zone; public holidays are not excluded) within which the team should decide a report. Shown to the reporter as "Review by".
- Default: not set.
- Values / limits: 1–90. New values apply only to new reports.
Public contact type
- What it does: How people contact the team about safety outside their account.
- Default: not set.
- Values / limits: Email or HTTPS (a web page).
Public contact
- What it does: The email address or the
https://page address for that contact. It appears on the public safety contact page and in safety emails. When the type is Email, the site shows its own public page at/?expertpress_messages_safety_contact=1with your explanation, the contact and the deadlines. - Values / limits: a valid email, or an
https://address up to 2000 characters.
Contact label
- What it does: The visible text of the contact link (per language).
- Values / limits: plain text, up to 160 characters, required for both languages.
Public explanation
- What it does: A short explanation of how safety reports are handled, shown on the public safety contact page (per language).
- Values / limits: plain text, up to 2000 characters, required for both languages.
Messaging rules URL (HTTPS)
- What it does: A link to your messaging rules, shown on the safety contact page (per language).
- Values / limits: an
https://address, required for both languages.
Insults and Threats word lists
- What it does: Messages and report details that contain one of these terms are refused with "The message contains insults or threats and was not sent. Please rephrase it." Both categories always use Reject.
- Default: empty (unless your theme or a site plugin supplies starting lists).
- Values / limits: one term per line: a word, a phrase, or a word beginning ending with
*(for exampleidiot*). Both languages are required for each category; up to 1000 lines per list, up to 200 characters per line; exact duplicates are removed. - When to change it: add new terms when reports show insults the filter missed; remove a prefix that blocks ordinary words.
Admin screens without options
Conversations
Where: ExpertPress → Messages → Conversations.
The list of booking conversations and complaint team chats, newest first, with the client, the specialist, the service, the booking number and a status pill (Open, Closed: service provided, Closed: booking canceled, Closed: money refunded, Closed: complaint, Closed: case resolved, or Complaint for flagged ones). Filters: Name or booking number and Status (All conversations, With violations (З порушеннями), Open, Closed). The list never shows message text.
Opening a conversation writes a row to the view journal first; if that fails, the conversation is not shown. Inside you see all messages and attachments, the Anti-bypass hits table (when, sender, category, rule, match), an Open booking link and:
- Verified (Перевірено) — clears the review flag after you checked the hits. If a new hit arrived meanwhile, the screen says "A new violation appeared."
- Hide message — next to a message with an open safety report; it opens that report.
- Reply as the team — in an open complaint team chat, when Reply from admin is on.
Safety
Where: ExpertPress → Messages → Safety (also Message safety in the moderation hub).
The queue of safety reports, in the tabs Open, In review and Resolved. Threats come first; overdue reports are marked Overdue but nothing happens automatically. Search by Report number (exact), Reason code (exact) or Participant ID, exact email or login.
A report shows its status, reason, the people involved, the deadlines, the reporter's details, the original evidence (opening it is logged) and up to ten earlier messages for context. Actions:
- Take for review, then Resolve report with a Decision: No violation found, Warning, Selected messages hidden, Personal sending restricted. A Public reply is required and may be sent to the reported author, so it must not name the reporter. Reason (10–2000 characters) is required for sanctions; Internal note is optional.
- Restore selected visibility / restriction — undo a hidden message or a sending restriction.
- Pair blocks — see the blocks between the two people and, for managers and administrators, Remove selected pair blocks with a reason.
Every action is written to the Safety journal shown under the record. The reporter and the reported person receive emails about decisions.
Support requests
Where: ExpertPress → Messages → Support requests.
Requests from specialists and safety requests from clients, filtered by Status (Open, Answered, Closed, All statuses) and Topic (Safety, Question, Bug, Review dispute). Inside a request: Reply as team (Відповісти від команди), Close and Reopen. Replies are signed as the team.
View journal
Where: ExpertPress → Messages → View journal. Title Message view journal.
Who opened which conversation and when (UTC), with a link to the conversation. Read-only. Retention: Keep journal for (days).