GURU SUPPORT DESK
Guru Support Desk compatibility with REEID Translate
Guru Support Desk compatibility with REEID Translate is being evaluated from available plugin evidence. Self-hosted WordPress helpdesk/ticket system with customer ticket creation and agent ticket desks (front-end and wp-admin) sharing the same underlying ticket data and core AJAX actions. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Guru Support Desk.
Official plugin information supports the compatibility context documented for this category.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
Guru Support Desk is documented in the Other category with 8 concrete capabilities identified in the current evidence.
EVIDENCE COVERAGE
Plugin capabilities are documented from available official evidence. Translation support is listed only when concrete visitor-facing content is explicitly established.
COMPATIBILITY REVIEW
How Guru Support Desk compatibility is evaluated
01 · Review official plugin evidence
Establish documented plugin behaviour before making any multilingual compatibility claim.
02 · Identify visitor-facing content
Determine whether the documented behaviour exposes human-readable values that visitors can see.
03 · Separate content from functionality
Keep structure, configuration, logic, integrations and runtime behaviour outside translation scope unless concrete content values are identified.
04 · Confirm translation scope
Publish supported content only when concrete visitor-facing values are explicitly established and can be validated.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- Self-hosted WordPress helpdesk/ticket system with customer ticket creation and agent ticket desks (front-end and wp-admin) sharing the same underlying ticket data and core AJAX actions.
- Ticket access control via built-in agent roles (Main Agent, Manager, Support Agent) where Support Agents can be restricted to Only Assigned Tickets or All Tickets; Main Agent and Manager always see all tickets, and restrictions are enforced server-side.
- Inbound email ticket processing using IMAP with continuous mailbox reconciliation, automatic polling, cron health repair, resumable catch-up batches, failed-message retries, and isolation so a malformed/unsupported email does not block newer mail.
- Persistent ticket CC participants with per-reply CC selection; CC participation is email-based and does not grant customer portal ownership; CC participants can reply into the existing ticket while unknown senders cannot inject into an existing ticket.
- Rich reply and note editing including rich text, searchable emoji picker, and inline pasted/dragged images; supports private Internal Notes that are excluded from customer-facing output and are never emailed to the primary customer or CC participants.
- Private attachment storage and access control: attachments are stored privately under the site uploads directory (below `uploads/guru-support-desk/private`) and are delivered through permission-checked WordPress handlers rather than public file URLs; accepted attachment types are limited to specific document/image formats.
- Email delivery configuration supports either WordPress mail (`wp_mail()`) or an optional dedicated SMTP transport; customer-facing replies use configured Reply-To routing with fallback order (From Email, then IMAP Username, then SMTP Username).
- Diagnostic logging enabled by default with 10-day retention, accessible via Settings > Logs (including a Download Logs button), and log contents are not rendered in the WordPress admin page.
CONTENT BOUNDARY
Guru Support Desk capabilities and translation scope are documented separately.
The available evidence documents plugin functionality, but does not currently establish a specific visitor-facing translation surface.
Functional capability alone is not treated as evidence that a value should be translated.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
COMMON QUESTIONS
Guru Support Desk and REEID Translate FAQ.
What does Guru Support Desk do according to the available plugin evidence?
Guru Support Desk has 8 concrete capabilities documented from the currently available official plugin evidence. See the Plugin Intelligence section for the individual capabilities.
Is a REEID translation surface currently confirmed for Guru Support Desk?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Guru Support Desk?
The evidence must identify concrete visitor-facing values such as labels, titles, descriptions, messages or other human-readable content that can be validated through the integration workflow.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Evaluate Guru Support Desk in a multilingual WordPress workflow.
REEID documents Guru Support Desk functionality separately from evidence-backed translation support so compatibility claims remain specific and testable.
Translation scope will be published when concrete visitor-facing content is established by evidence.