Helping Customers Without Overstepping: Support Access Done Carefully

Some support problems are hard to solve from the outside. A customer says a page looks wrong, a setting will not save or a workflow is confusing, and the quickest way to understand is to see exactly what they see. Our platform allows authorized members of our team to do that, carefully.

Support access is powerful. It lets someone act inside another organization's account. So we treat it with the same care as any other privileged action: limited, recorded and bound by rules that protect the customer. Here is how.

Only authorized staff

Support access is available only to a small number of authorized central administrators. Customers' own administrators cannot use it to enter other organizations, and ordinary staff accounts do not have it. Access is tied to individual accounts, so every action is attributable to a specific person.

The account and website are confirmed

Before acting inside an organization's account, the person confirms exactly which account and which website they are working in. In a platform with many organizations, entering the wrong account is a real risk, and confirming the context first prevents it.

Restraint is the rule

Being inside an account does not mean doing everything possible there. Support staff look at what the problem requires and make changes only when the customer has asked for help with them. Viewing private data that is unrelated to the problem, changing settings out of curiosity or tidying things the customer did not mention are all outside what support access is for.

Held features stay held

Features that are on hold for customers stay closed during support access too. A module that is not released to organizations is not reachable just because a staff member is working inside an account. Support access is not a side door into unfinished features, as explained in holding unfinished features back.

Onboarding help is not billed to the customer

When our team helps a new organization set up its site during onboarding, staff can use internal AI help inside that account to prepare drafts. That help is recorded and is not charged to the customer. The customer's own use of AI features afterward follows normal billing. We describe that boundary in separating internal AI tools from customer AI features.

Queued work rechecks access

If support work starts something that runs in the background, such as preparing a draft, the background job rechecks that the staff member still has access and is still working with that account before it continues. Access that has ended does not keep acting through queued work.

Everything is recorded

Support access and the actions taken during it are recorded with who did what and when. Records protect customers, who can trust that access is accountable, and protect our team, who can show exactly what was done if questions arise.

Payments and money need extra approval

Even with support access, some actions are off-limits without explicit approval: purchases, refunds, changes to payment settings and anything that spends money from an organization's wallet. Helping a customer understand their billing is support. Moving their money is a separate decision with its own safeguards.

Signing in still requires strong protection

Support access starts from a staff member's own signed-in account, which follows the same sign-in protections as every other account, including two-factor checks for people who have them turned on. Strong sign-in protection matters even more for accounts that can help many organizations.

Fixing the cause, not just the account

When support access reveals a bug, the fix goes into the platform through the normal pipeline rather than being patched by hand in one customer's account. That way the problem is fixed for everyone who might hit it, and the change is reviewed and recorded. Support is often where we learn the most about how the platform really behaves.

Customers can ask

Organizations can always ask what support access was used for on their account. Being able to answer that question clearly is part of earning the trust that makes support access acceptable in the first place.

Frequently asked questions

Can Jag Journey staff access my account?

Only a small number of authorized staff can, when needed to help you, and their actions are recorded.

Can support staff spend money or issue refunds in my account?

Not without explicit approval. Payment and money actions have separate safeguards beyond support access.

Am I charged when your team helps me set up my site?

Onboarding help from our team is not charged to your account.