MokoConsulting/MokoSuiteSupport
1
0
Fork 0
generated from MokoConsulting/Template-Joomla
Code Issues 11 Pull Requests Packages Projects Releases 1 Wiki Activity

ROADMAP — MokoSuiteSupport implementation plan #8

New Issue
Open
opened 2026-06-21 16:14:43 +00:00 by jmiller · 0 comments
jmiller commented 2026-06-21 16:14:43 +00:00
Owner
Copy Link
Copy Source

MokoSuiteSupport Roadmap

Live chat and multi-channel customer support for Joomla 6.

P0 — MVP

  • [#1] Initial scaffold — live chat component + widget
  • [#2] CRM and ticket system integration
  • [#7] Agent workspace — unified inbox

P1 — Multi-Channel

  • [#3] Facebook Messenger channel
  • [#4] Instagram Direct channel
  • [#5] WhatsApp Business channel
  • [#6] Email channel

Architecture

  • Layer: Standalone (optional CRM integration)
  • Channels: Website chat, Facebook, Instagram, WhatsApp, Email
  • Real-time: WebSocket with long-polling fallback
  • Unified inbox: All channels in single agent view

Competitive Landscape

  • Our advantage: Native Joomla integration, CRM contact linking, ticket escalation, multi-channel in one plugin, no per-agent SaaS fees
## MokoSuiteSupport Roadmap Live chat and multi-channel customer support for Joomla 6. ### P0 — MVP - [ ] [#1] Initial scaffold — live chat component + widget - [ ] [#2] CRM and ticket system integration - [ ] [#7] Agent workspace — unified inbox ### P1 — Multi-Channel - [ ] [#3] Facebook Messenger channel - [ ] [#4] Instagram Direct channel - [ ] [#5] WhatsApp Business channel - [ ] [#6] Email channel ### Architecture - **Layer:** Standalone (optional CRM integration) - **Channels:** Website chat, Facebook, Instagram, WhatsApp, Email - **Real-time:** WebSocket with long-polling fallback - **Unified inbox:** All channels in single agent view ### Competitive Landscape - **Our advantage:** Native Joomla integration, CRM contact linking, ticket escalation, multi-channel in one plugin, no per-agent SaaS fees
Sign in to join this conversation.
Labels
Clear labels
breaking-change
Breaking API or behavior change
 ci-cd
CI/CD pipeline changes
 config
Configuration changes
 css
CSS/styling changes
 dependencies
Dependency updates
 deploy-failure
Deployment failed
 documentation
Documentation changes
 good first issue
Good for newcomers
 health-check
Repo health check result
 help wanted
Extra attention needed
 html
HTML/template changes
 joomla
Joomla extension
 major-release
Major version release
 minor-release
Minor version release
 mokostandards
Related to MokoStandards framework
 patch-release
Patch version release
 php
PHP code
 push-failure
Git push operation failed
 release-candidate
Release candidate build
 security
Security vulnerability or hardening
 size/l
200-500 lines changed
 size/m
50-200 lines changed
 size/s
10-50 lines changed
 size/xl
500+ lines changed
 size/xs
< 10 lines changed
 standards-drift
Deviates from MokoStandards
 standards-update
MokoStandards compliance update
 sync-failure
Sync or mirror failed
 version-drift
Version mismatch across files
 work-in-progress
Draft or incomplete work
No labels
Priority Medium
Type Feature
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
jmiller (Jonathan Miller)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: MokoConsulting/MokoSuiteSupport#8
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?