For Support Agent: Getting Started in SGEN
How to hit the ground running as a Support Agent
The Support Agent role is the human at the front of the queue. You answer customer questions about the site, look up account state, read the activity log, and route the harder problems to a teammate who can change something.
Your scope is deliberately narrow. You can read most of the admin. You can search content, comments, orders, and users. You cannot publish posts, change settings, or remove anyone from the account. That separation is the role. Configuration changes belong to a Platform Admin or the named role for that surface.
This guide walks you through the surfaces you have, the surfaces you do not have, the day-one routine that builds context fast, the daily and weekly rhythm that keeps the queue from growing, and the escalation paths that keep you from sitting on something you cannot fix.
30-second pitch for the role
You are the first read on every incoming question. You see what the customer sees, plus a layer of context — recent posts, recent orders, recent comments, account history. You answer when the answer is in front of you. You escalate when the answer needs a change. The role rewards pattern recognition: the same five questions are 80% of the queue, and you build the muscle to spot them in the first sentence of the message.
What is this for?
The Support Agent role is for the teammate who triages incoming customer messages and resolves the ones that do not require a configuration change. Typical scenarios: a customer asks why a post is not showing on the site, a comment got flagged as spam and the customer wants it back, an order is sitting in pending, or a form submission did not arrive.
You read the admin to confirm what the customer is describing. If the fix is on the customer's side (a typo in their search, a setting on their own browser, a permission on their own account), you walk them through it. If the fix is on the admin side (a missing category, a draft that needs publishing, a refund that needs approval), you escalate to the role that can change it.
Good use cases
- A reader emails saying "your blog post about brewing methods is missing" — open Blog in the admin, search the title, confirm the post is in Draft, escalate to the Content Editor with the post ID and a one-line note.
- A customer says a comment they posted is gone — open Discussions, filter to Spam, confirm whether their email matched a spam pattern, decide whether to escalate to a moderator to approve.
- A shopper reports an order stuck at "pending" — open Orders, search the order number, read the activity timeline, and either confirm payment is captured or escalate to the Ecommerce Manager.
- A form submission "never arrived" — open Forms, look at the recent-submissions log, confirm whether the submission landed but routed to spam, or whether the form itself is misconfigured.
- A reader asks where a page went — open Pages, search the title, check whether the page is in Trash or unpublished.
What NOT to use this for
- Changing site settings. Email routing, payment provider keys, cookie banners — none of these belong to the Support Agent role. Escalate to Platform Admin.
- Editing or publishing content. You can read a draft. You cannot change it. If the customer is right that the draft has a typo, route to the Content Editor with the post ID and the requested change.
- Removing users from the account. User removal is a Platform Admin action. You can see the user record. You cannot delete it.
- Issuing refunds or changing prices. Money movement belongs to the Ecommerce Manager (or the Platform Admin on accounts without an Ecommerce Manager).
- Promising feature timelines. If a customer asks "when will X ship," route the question to the team that owns the roadmap. You do not speak for unreleased work.
- Pasting the raw activity log. The activity log contains internal account history. Summarize what you found; do not forward log entries verbatim to a customer.
How this connects to other features
- For Content Editor — most "post is missing" tickets escalate here. Know the Editor surfaces so your escalations land with enough context to act on.
- For Marketing Manager — forms, popups, and lead routing live in this role's surface. Form-submission tickets escalate here.
- For Platform Admin — settings, users, billing. Anything you cannot read or anything that needs to change at the account level escalates here.
- SGEN Glossary — terminology check before you reply to a customer. Use the platform's words, not synonyms from another CMS.
- FAQ — the canonical short answers to recurring customer questions. If a ticket matches an FAQ entry, link the customer to the FAQ in your reply.
Before you start
- Your account has been created and assigned the Support Agent role.
- You have received your login link by email.
- You are signing in at the customer's SGEN admin URL — the one shared by the Platform Admin on your first day.
- Your left navigation shows Blog, Pages, Discussions, Users, Orders (if the site sells), Forms, and Activity Log. Settings, Appearance, and most write actions are not visible.
- You have a modern browser and a stable connection — Chrome, Firefox, or Edge, current major version.
If the left navigation is missing a surface you expect to see, contact the Platform Admin. Your role may not be fully configured. Do not work around the gap. The role boundaries exist for a reason and you are not the person who decides to change them.
Where to go
The surfaces a Support Agent touches every day, and where each lives in the left navigation:
| Surface | Left nav path | What you do there |
|---|---|---|
| Blog | Blog → All Posts | Search post titles, confirm draft/published state, read revision history |
| Pages | Pages → All Pages | Locate a page by title, confirm its publish state |
| Discussions | Discussions → All Discussions | Look up a comment by author email, confirm Spam/Approved/Pending state |
| Users | Users → All Users | Look up a customer by email, confirm last-login, confirm role |
| Orders | Orders → All Orders | Search by order ID, read the timeline, confirm payment + fulfillment state |
| Forms | Forms → Submissions | Confirm a form submission landed; check spam-filter on entries |
| Activity Log | Settings → Activity Log (read-only) | Confirm a recent admin action (publish, role change, setting change) |
You will not see, and should not need: Settings (general site config), Appearance, Users → Add New, Billing, Theme Editor, Custom Codes, Custom CSS.
Steps
1. Open the queue and read the oldest message first
Pull up the ticket queue. Sort by age. Open the oldest message first — it is the one closest to a customer giving up. Read the message all the way through before opening the admin to look anything up. Customers describe what they see, not what is broken. The closer you stay to their words, the faster you find the right surface to check.
If the same customer has multiple tickets open, group them and reply once. Customers feel ignored when they get three separate replies from three separate agents.
2. Confirm what they describe by opening the matching admin surface
Translate the customer's words into a surface.
"My post about brewing methods is gone" → open Blog, search the title, look at the State column.
"The order I placed yesterday never confirmed" → open Orders, search the order ID, read the timeline.
"My comment was deleted" → open Discussions, filter Spam + Trash, search by author email.
Confirm the customer's description in the admin before you reply. Do not guess. The most common Support Agent mistake is replying from memory of how SGEN worked last week. The admin changes weekly; your reply must match what is true right now.
3. Resolve or escalate — never sit on a ticket
If the answer is in front of you (the post is in Draft, the order has a card-declined event, the comment is in Spam), draft the reply. Use the customer's words back to them. Keep the reply short. End with the next action the customer should take.
If the answer needs a change you cannot make, escalate. Include: customer email, ticket ID, the symptom in one sentence, the admin evidence in one or two more, and your recommended next action. Route to the role that can change the thing — Content Editor for content changes, Marketing Manager for forms and campaigns, Ecommerce Manager for orders and refunds, Platform Admin for settings and users.
Do not escalate without first confirming the symptom in the admin. A blind escalation is a longer ticket, not a faster one.
4. Update the ticket so the next agent can pick it up
Every ticket you touch gets a one-line note before you close the tab. The note answers three questions: What did you find? What did you do? What is the next step (and whose)?
The next agent picking this ticket up tomorrow has zero context unless you wrote it down. A ticket "in your head" is a ticket that gets re-investigated by whoever opens it next.
5. Note the patterns at end of day
At end of shift, scan the tickets you closed. What were the top three categories — content, comments, orders, forms, account? Were any tickets the same question worded differently? If three customers asked about the same form this week, the form is probably misconfigured, not the customers.
Send the pattern note to the team channel. You are the first to see emerging issues. Your pattern report is how the team catches a problem at ticket #3 instead of ticket #30.
Day-one checklist — first five things to do
Before your first triage shift, walk this checklist top to bottom. Each item gives you context the queue assumes you already have.
- Log in and confirm your left navigation. Blog, Pages, Discussions, Users, Forms, Activity Log should all be visible. Settings and Appearance should not be. If the layout does not match, contact the Platform Admin before opening any tickets.
- Bookmark the public-facing docs site for your account. Most customer questions can be answered with a link to the docs. Use the public URL the customer would see, not the staging URL only your team has access to.
- Read the SGEN glossary end to end. Twenty minutes. The vocabulary mismatch is the most common cause of a reply that confuses the customer further.
- Skim the FAQ. The same five questions repeat across most queues. Knowing the canonical short answers means you can reply faster and consistently.
- Pair with a senior teammate for one shift. Watch them triage three tickets before you take one solo. Pattern-matching is faster to learn by watching than by reading.
Day-two through week-two progression
The role compounds across two weeks. The first week you build vocabulary and pattern recognition. The second week you build judgment about when to escalate.
| Day | Focus | Concrete output |
|---|---|---|
| Day 2 | Solo triage on lowest-complexity tier · paired review at end of shift | First five tickets closed with senior sign-off |
| Day 3 | Solo triage on medium-complexity tier | First independent close · first one-line ticket note in handover format |
| Day 4 | Read the past 30 days of escalations · understand the receiving roles | One escalation written without senior coaching |
| Day 5 | Full shift on the standard queue | End-of-week pattern note filed |
| Week 2 Mon | Begin handling 24h-aged tickets | One aged ticket cleared by end of day |
| Week 2 Wed | First proposal to add a recurring question to the FAQ | FAQ proposal routed to the docs lead |
| Week 2 Fri | First on-call shift coverage (if applicable) | Coverage handover note filed |
By end of week two, the role expectations stabilize: you handle the standard queue solo, you escalate cleanly, and your pattern notes feed the team's weekly review.
Key surfaces this role uses
Five surfaces carry the daily work. Memorize the path to each — the speed of your triage is set by how quickly you can move between them.
- Blog (All Posts) — confirm post existence and state for any "where is my post" question.
- Pages (All Pages) — the static-page equivalent of the blog check.
- Discussions (All Discussions) — confirm comment moderation state.
- Users (All Users) — confirm account existence, role, and last-login.
- Orders (All Orders) — confirm order state for any sales-related ticket.
Key surfaces this role does NOT use
The surfaces below are visible to other roles but not to you. That is the boundary that defines the Support Agent role. If you find yourself wanting access to any of them, that is the signal a ticket should escalate, not a request to expand your role.
- Settings (any sub-tab). Email, payments, integrations, cookie banners — all out of scope.
- Appearance. Theme settings, layout, branding.
- Users → Add New, Edit Role, Delete. You can read user records. You cannot modify them.
- Billing. Plan changes, invoices, payment methods — Platform Admin only.
- Custom Codes / Custom CSS. Developer surface only.
- Theme Editor. Developer surface only.
What success looks like
A healthy week for a Support Agent looks like:
- First response on every ticket within the SLA window the customer was sold.
- Queue depth at end of day matches queue depth at start of day, plus or minus a few — you are keeping pace with inflow.
- Escalations leave with enough context that the receiving role can act without coming back to you for clarification.
- Pattern notes go out at least once a week — one or two patterns spotted across the week's tickets.
- Customer replies cite the platform's words, not synonyms — "post is in Draft" rather than "post is hidden."
Common questions for this role
"I can read the order — can I refund it?" No. Refunds are an Ecommerce Manager action. You can confirm a refund was issued (by reading the timeline). You cannot issue the refund yourself.
"The customer wants their account deleted. Can I do that?" No. Account deletion is a Platform Admin action and usually has a waiting window. Escalate with the customer's request in writing.
"Where do I look up the activity log?" Settings → Activity Log. You have read access. You cannot clear or edit entries.
"How do I reply to a comment thread on a post?" You do not. Comment replies are a Content Editor or Marketing Manager action — they reply as the brand. You can confirm the comment is approved. The reply itself belongs to a role with a public voice.
"The customer is asking when feature X ships. What do I say?" "That question goes to our roadmap team — I have routed your message to them and they will follow up directly." Then route it. You do not speak for unreleased work.
"A customer is asking me to bend a policy — what do I do?" Restate the policy and offer the escalation path. "That request needs sign-off from a Platform Admin. I have routed your message and you should hear back within one business day." Do not bend the policy yourself.
What to do if it does not work
You cannot see Users, Orders, or Activity Log in the left navigation.
Your account may not have the Support Agent role assigned, or the role configuration is incomplete. Contact the Platform Admin and ask them to verify your account. Your role field should show Support Agent. Do not work around the gap by asking another teammate to look something up for you — that defeats the audit trail.
A customer is asking about a post you cannot find in Blog.
Try Pages — the customer may have called it a "post" but it is a static page. Also try the Trash tab in both Blog and Pages. If still not found, the post may never have existed, or it was permanently deleted. Reply to the customer asking for the URL they were trying to reach, not the title — the URL is the unambiguous reference.
Your search returns "no results" but you know the record exists.
Search by email instead of name (or vice versa). Search is exact-match in most surfaces; partial names rarely return what you expect. Try the email domain alone — for example, search yourdomain.com to surface every user from that domain.
A ticket has been with you for over 24 hours with no clear next step.
Escalate to your team lead, not to silence. The escalation note should include: what you have already checked, what you cannot determine without elevated access, and what the customer is waiting on. Sitting on a ticket past 24h is the failure mode that turns a small frustration into a churn risk.
The customer's question turns out to be a feature request.
Acknowledge the request. Route it to the channel where product takes input. Reply to the customer confirming the request was received and where to follow updates. Do not promise a timeline.
Other roles on this site
Each role on a SGEN site has its own onboarding guide. The table below maps ticket categories to the role you escalate to.
| Role | When to route to them |
|---|---|
| Content Editor | Post is in Draft, page is unpublished, media is missing — any content-state change |
| Marketing Manager | Form submission not arriving, popup not showing, blog post not in the queue |
| Ecommerce Manager | Order stuck in pending, refund needed, product not showing in the store |
| SEO Specialist | Customer reports a broken link or 404 — pass the path and the hit count |
| Developer | Checkout layout broken, tracking not firing, custom code behaving unexpectedly |
| Platform Admin | Settings change needed, user account issue, billing question |
| Partner / Agency | If the site is agency-managed, route structural issues through the agency contact |
Cross-link to deeper docs
- SGEN Glossary — confirm terminology before replying. Customer-facing language is the platform's language, not synonyms borrowed from another CMS.
- FAQ — recurring customer questions and their canonical short answers. Link the customer to the FAQ when the question matches.
- For Content Editor — the surfaces you escalate content tickets into.
- For Marketing Manager — the surfaces you escalate form and campaign tickets into.
- For Platform Admin — the surfaces you escalate settings, billing, and user-management tickets into.
- For Ecommerce Manager — the surfaces you escalate order and refund tickets into.
- For SEO Specialist — the surfaces you route broken-link and 404 reports into.
- For Developer — the surfaces you escalate code-level and checkout issues into.