Private support access for real inbox ownership and clear follow-up
This workspace exists for people handling private app follow-up, support replies, and inbox triage that should not disappear into Discord threads or personal inboxes.
Use this page if your role is support. Admins work inside the Dancz Ministries plugin instead.
Use this page when you need private follow-up, not public chatter
The support role is for people who need to read inbound app mail, keep internal notes, reply with the right sender identity, and hand issues forward without losing context.
Best fit
Support agents and follow-up owners
This role fits the people who need to answer questions, track message state, and keep private app support moving inside WordPress.
What lives here
Inbox triage, notes, and reply flow
Use the Mail Center to read inbound mail, add internal notes, mark status, and reply from the site without relying on personal inboxes.
What to avoid
Do not use this page for broad admin work
If the issue becomes a provisioning task, permissions change, or executive decision, hand it to operations or executive review instead of stretching support beyond its scope.
Support should feel private, accountable, and easy to hand off
Public Discord is still useful for community and beta energy. It is not the right place for every private follow-up, internal note, or sensitive reply.
This workspace gives Dancz Ministries a calmer support surface with clearer ownership and less dependence on memory or scattered handoffs.
- Private support follow-up
- Consistent reply identity
- Internal notes and message state
- Cleaner escalation into operations
Private app mail routes through ruachdavidapp@danczministries.com
That address is meant to land in the protected workflow so support stays bounded, visible, and easier to review.
A simple flow keeps private support human and traceable
The point is not extra process. The point is making sure each message has a clear home, current state, and next action.
Sign in
Use the role login page to enter the protected Mail Center with the account already assigned to support.
Triage
Review sender, subject, preview, and history so the message lands in the right state before you reply.
Reply or escalate
Respond here when support owns the next step, or escalate when the issue becomes operational or executive.
Close cleanly
Leave the current state visible so another person can reopen context without reconstructing the whole story later.
Request access before sharing credentials
If you do not already have the support role, use the ministry contact page and ask for the correct access to be assigned to your own account.
Request Support AccessOpen the Mail Center login page.
Use the dedicated login page first. If you still need the role, request support access instead of trying to enter the protected workspace directly.
If the question is public beta conversation rather than private follow-up, route that person to Discord Beta instead.