Front Line
AI Customer Support Agent
Resolves customer questions across chat and email using your knowledge base and hands off complex cases.
Extensions
Admin Playbook and SOP Pack
Whoever looks after the product has written steps for every routine task, so nothing depends on one person's memory.
When only one person knows how the AI product is looked after, holidays and resignations become risks. This pack gives your admins written procedures for every routine task, such as updating knowledge, checking logs or handling a fault. Each procedure is written in numbered steps and checked against your live setup, so anyone trained can follow it.
- Writes every routine admin task as numbered steps
- Checks each procedure against your live setup
- Removes the risk of relying on one person's memory
$1,500
10–20 working days
What it is
Admin Playbook and SOP Pack is an add-on that gives the admins of an Upmark Labs product written operating procedures. Each procedure covers one routine task, such as updating knowledge, checking logs or handling a fault, in numbered steps. Each one is checked on your live setup.
Why businesses buy it
Knowledge that lives in one person's head disappears when they leave, and small mistakes during routine updates can take an AI product offline or change its answers. Written procedures make upkeep repeatable, speed up training for new admins and give auditors something concrete. The written scope covers the admin tasks agreed at intake, each written as numbered steps and tested on your live product, with one revision round, so the playbook matches how your setup actually works.
Problems this solves
Routine admin tasks live in one person's head
The Admin Playbook and SOP Pack writes each routine task down as a numbered procedure. Updating knowledge, checking logs or handling a fault no longer depends on one person remembering the steps.
A fault happens and nobody knows the safe first step
Fault handling is covered by its own written procedure, step by step. Whoever is on hand can follow it calmly instead of guessing or waiting for the usual admin to return.
Written guides drift away from how the setup really works
Each procedure is checked on your live setup before handover. The steps match what admins will actually see on screen, rather than a generic template written elsewhere.
A good fit if
One person knows how the product is run, and you would be stuck if they were away.
You need procedures on file for internal reviews, audits or handovers between staff.
Your admins prefer a written checklist they can follow over a recording they have to scrub through.
You run an Upmark Labs product, or this add-on is part of the order for one.
Not the right fit if
You only need the basics. Every Upmark product already comes with an admin guide and a written handover report.
You want recordings and notes from across the business turned into procedures. AI SOP Generator does that.
You need documentation of data flows and controls for compliance reviews. Compliance Documentation Pack is written for that.
You want the work done for you each month rather than written down. Monthly maintenance covers ongoing changes instead.
How it works
- Admin tasks are listed. We go through what your admins will need to do, from routine checks to rare fixes.
- Each task is written as a procedure. Numbered steps, who does it, how often, and what to check afterwards.
- Escalation is spelled out. Each procedure says when to stop and contact support, or us through your monthly maintenance.
- Procedures are tried on the parent product. We follow each one against the live setup to make sure the steps work as written.
- You review the pack with one revision round, then receive the final version and a written walkthrough.
What you provide within 72 hours
Your portal lists these the moment you order. Delivery starts the working day after everything is in and your access is checked.
- The order reference of the product the playbook covers
- Who your admins are, and what they will be responsible for
- Any internal format or template your procedures must follow
- Tasks your admins already find confusing or error-prone
- One person who approves the final pack
The 72-hour rule. Send everything on your checklist, including access, within 72 hours of ordering so your build starts on time.
Timeline
Start
Admin roles and task list collected
Weeks 1–2
Procedures drafted task by task
Week 2
Each procedure followed on the live product
Week 2
Draft pack sent for your review
Week 2
One revision round applied
Go-live
Final playbook and written walkthrough delivered
| Option | Delivery time | Price |
|---|---|---|
| Standard | 10–20 working days | $1,500 |
What you receive at handover
- Written operating procedures for your admins, one routine task per procedure
- Procedures checked against your live setup
- Updated product documentation and a test report
- A handoff note and a short written walkthrough
Expected benefits and how to measure them
- Helps more than one person run the product with confidence
- Can make holidays and staff changes less disruptive
- Makes routine tasks more consistent from one admin to the next
- People able to do each task
- List who can perform each routine task before handover and again a quarter later.
- Time to resolve faults
- Log the time from noticing a fault to fixing it, comparing incidents before and after.
- Repeat admin questions
- Ask the lead admin to count how-to questions from colleagues each month, before and after.
Before you start: List the routine admin tasks and who can do each one today. Note how long recent faults took to fix.
These are things to track, not promised results. Outcomes depend on your data, your team and your market.
Running costs
Written procedures add no running cost. The product's own usage stays billed to your accounts as before.
Ask about running costsCustom requirements
Translating the pack, writing procedures for systems outside the product, or loading it into your own knowledge tool is beyond this add-on. Add it to the checkout note for a written Change Quote. Larger or bespoke projects go through the Custom AI request form instead.
Request a custom versionKeep it running
When the product changes, the affected procedures should change too. Updates come out of the parent product's monthly maintenance hours, which grow in line with this add-on's price, so there is room to keep the playbook current.
Adds $75/mo to maintenance
Covered by the main product's maintenance, which grows by this amount.
How maintenance worksHow this compares
| Do it yourself with a SaaS tool | Hire a custom agency | Upmark Labs | |
|---|---|---|---|
| Price | Vendor help pages are free but generic | An agency bills documentation by the day | Ours is one fixed price, shown before you buy |
| Fit | Written for every customer | Depends on the brief | Ours is written for your setup and your admins |
| Accuracy | May not match your configuration | Set per project | Ours is checked step by step on your live product |
Questions about this product
What tasks does the admin playbook cover?
The routine and occasional tasks your admins will perform on this product, agreed at intake. Typical examples are updating knowledge or FAQs, checking logs, reviewing flagged conversations, changing who receives alerts, and what to do when something fails. Each becomes a numbered procedure with a clear owner and frequency.
What format is the SOP pack delivered in?
A document you can edit, organized with one procedure per section. If your company already has a procedure template, give it to us at intake and we write into that format. Loading the pack into a separate knowledge tool or intranet is not included, but can be quoted.
How do you make sure the steps actually work?
We follow every procedure ourselves on the live parent product before you see the draft. Where a step does not behave as written, the procedure is corrected. That check is why the pack matches your configuration rather than a generic version of the product.
Does the playbook tell admins when to call for help?
Yes. Each procedure has a stopping point that says when the problem is beyond routine admin work, and who to contact: our support during the 14 days after delivery, then us through your monthly maintenance. That keeps admins from making risky changes on their own.
Can the playbook be written for a product we already run?
Yes. For a live product, every procedure is written and checked against the setup as it runs today. If you are buying the product now, the pack follows its delivery speed and is finished once the configuration is final. Each speed has a fixed price and date shown before you pay.
How is the playbook different from the admin guide?
Every Upmark product comes with an admin guide and a written handover report that explain how it is set up. The playbook goes further. It turns each routine task into numbered steps with an owner and a frequency, checked on your live setup. New admins can follow it without asking anyone, and questions during the 14 days of support are answered by email.
Write down how the product is run, before you need it.
Add the Admin Playbook and SOP Pack and your admins get numbered procedures for every routine task, each one checked on your live setup.
Works well with
Workflow Automation
AI Multi-Step Workflow Automation
Automates an end-to-end business process across several systems with AI decisions.
