Internal Training Guide

MIQ Training Manual

Complete operator training guide for the MIQ platform — subscriptions, billing, estimates, tickets, e-signatures, and team management.

🏢 What Is MIQ?

MIQ (Command Center) is the internal operations platform for Solution Monsters. It is used exclusively by the Solution Monsters team — it is not a self-service portal for end clients.

MIQ handles everything needed to run SCOPE as a SaaS business:

Subscription Management

Create, provision, and manage SCOPE subscriptions. Track tiers, billing cycles, payment status, and seat usage.

Client CRM

Maintain records for every client company, their contacts, and related employees.

Estimates & Work Orders

Build estimates with change orders, collect signatures, approve into work orders, and track billing progress.

Support Tickets

Receive, assign, and resolve support tickets from SCOPE tenants, email intake, or manual creation.

E-Signatures

Collect legally-binding digital signatures on change orders — internal (typed/drawn) or external (email link).

Vault

Encrypted credential storage (AES-256) for passwords, API keys, and sensitive team credentials.

👤 Roles & Permissions

MIQ has five roles. Access is enforced at the API level — users cannot see or reach pages they don't have access to.

RoleWho It's ForWhat They Can Do
Admin Founder / lead operator Full access to everything. Only role that can manage user accounts, soft-delete records, and administer vault access.
Manager Operations manager Create/edit companies, contacts, employees, subscriptions, estimates, work orders, change orders, tickets. Cannot manage user accounts or delete records.
Accounting Finance team Full subscriptions and vault access. No sidebar access to companies, contacts, employees, estimates, work orders, or tickets.
Tech Support engineer Create, assign, and resolve tickets. Vault access. No sidebar access to companies, contacts, employees, subscriptions, or estimates.
Viewer Analyst / intern Read-only access across all modules. Cannot create, edit, approve, sign, or delete anything.

Permission Matrix

Module Admin Manager Accounting Tech Viewer
Dashboard
CompaniesCRUDCRUDView
ContactsCRUDCRUDView
EmployeesCRUDCRUDView
EstimatesCRUD + ApproveCRUD + ApproveView
Work OrdersCRUDCRUDView
Change OrdersCRUD + SignCRUD + SignView
SubscriptionsCRUD + ProvisionCRUD + ProvisionCRUD + Provision
TicketsCRUD + AssignCRUD + AssignCRUD + AssignView
VaultFull + Access CtrlIf grantedIf grantedIf grantedIf granted
User AccountsCRUD + Reset
Soft-Delete Records

📊 Dashboard

The dashboard is your starting point when you log in. It shows live business metrics at a glance.

  • Open Tickets — count of all tickets with OPEN status across all assignees
  • My Open — tickets assigned to you that are not yet resolved
  • Past Due Subs — subscriptions currently in PAST_DUE status
  • Bills Due (14 D) — subscriptions billing within the next 14 days

Click any tile to navigate directly to that module. Below the tiles, the My Tickets and Open Tickets tables show your assigned and recent open tickets. Past Due Subscriptions and Upcoming Bills tables appear alongside them.

🏗️ Companies & Contacts

Companies

Every SCOPE client lives in the Companies module. Each company record holds:

  • Company name, mailing address
  • Primary contact name, email, phone
  • SCOPE URL — a link directly into the client's SCOPE tenant
  • Stripe customer ID (auto-linked when a subscription is provisioned)
  • Internal notes

To create a company: Companies → New Company. Fill in the name and address, then save. The Client ID shown on the detail page is the unique identifier that links this company to their SCOPE tenant — you'll use it when setting up their SCOPE integration.

Contacts

Contacts belong to a company and represent individuals you'll communicate with. Key flags:

  • Primary Contact — the main point of contact for the company
  • Billing Contact — receives invoices and billing emails

Each contact can have multiple email addresses and phone numbers, each labeled by type (work, mobile, billing, etc.).

📋 Estimates & Work Orders

Estimates and Work Orders are the same record type — the difference is that an estimate becomes a work order once it's approved and assigned a WO number.

Both use a two-panel layout: a year-filtered sidebar on the left lists your records; clicking one opens the detail view on the right.

Estimates

An estimate represents proposed work before approval. To create one:

New Estimate — click "New Estimate" in the sidebar. Select the company. The system auto-generates an estimate number.

Add Change Orders — estimates contain one or more change orders (see Change Orders section). Click + Add CO to add line items with descriptions, pricing, and scope.

Approve — once the estimate is ready, click "Approve." The estimate moves to Work Orders and receives a WO number.

Work Orders

Work orders are approved estimates in progress. They gain three additional tracking fields per change order:

  • Billed — amount invoiced to the client
  • Received — amount the client has paid
  • % Completed — progress toward completion (0–100%)

Update these as work progresses to keep accurate billing records.

📝 Change Orders

Change orders (COs) are the line items within an estimate or work order. Each CO captures:

  • CO number and revision
  • Description, location, scope of work, qualifications, comments
  • Estimator (employee) and company representative (employee)
  • Customer name, price, status
  • Estimated hours: straight time (ST) and overtime (OT)
  • Dates: creation, due date

CO Actions:

  • Edit — update any field before approval
  • Revise — create a new revision when scope changes. The CO number stays the same; the revision number increments. Previous revisions remain in the system.
  • Sign — collect an internal or external signature (see E-Signatures)
  • Request Signature — send an email signing link to a client
  • Email CO — send the CO as a formatted email (informational, no signature required)
  • Attachments — upload PDFs, images, or documents (10MB limit per file)
  • Export PDF — download a letter-format PDF of the CO

✍️ E-Signatures

MIQ collects legally-binding digital signatures on change orders. All signatures include an IP address, user agent, timestamp, timezone, and a SHA-256 tamper-evident hash. Once recorded, a signature cannot be edited or deleted.

Legal basis: Signers must check two consent checkboxes before signing: (1) consent to use electronic records and signatures for the transaction, and (2) certification that the electronic signature is valid and binding. Both are required. This satisfies ESIGN Act requirements.

Internal Signing (you sign on behalf of a party)

Open the CO and click Sign.

Enter the signer's full legal name and email address — both are required and captured in the audit record.

Choose Type (name displays in cursive) or Draw (sign on the canvas pad).

Check both consent checkboxes, then click Sign. The signer's timezone is captured automatically — no selection needed.

The signature is recorded and displayed permanently on the CO detail.

External Signing (client signs via email link)

Open the CO and click Request Signature.

Enter the recipient's email, subject, and an optional message. Submit.

The client receives an email with a unique one-time signing link.

The client clicks the link, views the CO details (read-only), signs using typed or drawn method, accepts the legal consent checkbox, and submits.

You receive a confirmation email: "Signature received from [name]." The link is automatically invalidated — it cannot be used again.

💳 Subscriptions & Billing

The Subscriptions module is the core of MIQ's billing operations. It manages every SCOPE tenant's subscription, Stripe integration, invoicing, and seat usage.

Subscription Statuses

  • TRIAL — active trial period; SCOPE is accessible
  • ACTIVE — paid and current
  • PAST_DUE — payment failed; SCOPE shows warning banner
  • SUSPENDED — access manually suspended by operator
  • CANCELLED — subscription ended; SCOPE enters 7-day read-only grace period, then blocks access

Pricing Tiers

TierUsersMonthlyAnnual
StarterUp to 3$149/mo$124/mo
GrowthUp to 7$249/mo$191/mo
ProUp to 15$349/mo$291/mo
BusinessUp to 50$599/mo$499/mo
EnterpriseUnlimitedCustomCustom

Creating & Provisioning a Subscription

Navigate to Subscriptions → Create Subscription. Select the company, tier, billing cycle (monthly or annual), user limit, price, and collection method.

Click Provision. MIQ creates a Stripe customer (if one doesn't exist) and a Stripe subscription. Status is set to TRIAL.

If the client will be charged automatically, click Setup Payment to email them a Stripe billing portal link where they add their card.

Stripe webhooks keep MIQ in sync — when the client pays, status moves to ACTIVE; if payment fails, it moves to PAST_DUE.

Sending a Custom Invoice

Open a subscription and click Send Invoice.

Add line items (description and amount). Toggle "Send to Client" to email the invoice to the billing contact. Add CC/BCC for internal copies.

Submit. MIQ generates a Stripe invoice and sends the email.

Overage Billing

If a tenant's seat count exceeds their tier limit, MIQ calculates a per-seat overage charge. This is tracked automatically when SCOPE reports seat counts via the API.

🎫 Support Tickets

Tickets can arrive from three sources:

  • SCOPE Intake — a SCOPE tenant submits a support request from within their app
  • Email Intake — forwarded email is automatically parsed into a ticket
  • Manual — an operator creates a ticket directly in MIQ

Ticket Workflow

Ticket arrives in the OPEN queue. Assign it to a team member using the "Assign to" dropdown.

Move the status to IN_PROGRESS when work begins.

Add comments — choose direction: INBOUND (from client), OUTBOUND (to client), or INTERNAL (operator note only). Attach screenshots or files as needed.

If waiting on the client, set status to WAITING_ON_CUSTOMER.

Once resolved, set status to RESOLVED, then CLOSED to archive.

Ticket Priorities

  • URGENT — system down, data loss, security issue
  • HIGH — major feature broken, blocking client work
  • NORMAL — standard issues and questions
  • LOW — minor cosmetic issues, feature requests

👥 Employees

The Employees module stores your internal team roster. Employee records serve two purposes:

  • Used as Estimator and Company Representative dropdowns on change orders
  • Linked to User Accounts for login access

Job title matters for dropdown ordering — employees with the "estimator" title sort first in the Estimator dropdown; those with "sales" sort first in the Representative dropdown.

🔐 Vault

The Vault is an AES-256 encrypted credential manager for storing passwords, API keys, and sensitive team credentials. All data is encrypted at rest and decrypted only on the client side.

  • Organize entries into folders/groups (hierarchical)
  • Each entry stores: title, username, password, URL, notes, optional expiration date
  • Passwords are masked by default — click to reveal
  • One-click copy to clipboard for username, password, or URL
  • File attachments per entry (API keys, certificates)
  • Export entire vault as an encrypted .psafe3 file (Password Safe format) for backup
Access Control: Vault access is granted per employee by an Admin. Each employee can be assigned ADMIN, EDITOR, or VIEWER access to the vault. No access by default.

🔑 User Accounts

Admin only. This module manages login credentials and role assignments for all MIQ operators.

Go to User Accounts → New Account. Enter a username, assign a role, and optionally link to an employee record.

Click Send Temporary Password. The system generates a random password and emails it to the linked employee's email address.

The new user logs in with the temporary password and should change it immediately via their profile.

To deactivate a user, find their account and click Deactivate. Their record is preserved but they can no longer log in. Reactivate at any time.

🔗 Integrations

Stripe

Subscription provisioning, invoice generation, and automatic payment collection. Webhooks keep subscription statuses in sync in real time.

SCOPE (b2bdemo)

MIQ pushes subscription status, tier, seat limits, and enabled features to each SCOPE tenant. SCOPE also submits support tickets and seat counts to MIQ via API.

SMTP2GO (Email)

All outbound emails — temp passwords, signature requests, invoice copies, and ticket notifications — route through SMTP2GO via mail.smtp2go.com.

Cloudflare R2

Ticket attachments uploaded from SCOPE are stored in Cloudflare R2. MIQ proxies download requests so files are accessible in the ticket detail view.

Key Workflows

Onboarding a New SCOPE Client

Create Company — Companies → New Company. Fill in name, address, and primary contact details.

Add Contacts — add the billing contact and primary operator. Flag the billing contact so they receive invoices.

Create Subscription — Subscriptions → Create. Select the company, tier, billing cycle, and collection method.

Provision in Stripe — click Provision. MIQ creates the Stripe customer and subscription. Status moves to TRIAL.

Send Payment Setup — click "Setup Payment" to email the client a Stripe billing portal link where they add their card.

Share Client ID with SCOPE — copy the company's Client ID from the company detail page and give it to the client to paste into their SCOPE → Subscription settings. This links their SCOPE tenant to MIQ.

Handling a PAST_DUE Subscription

Stripe webhook arrives: payment failed. Subscription status changes to PAST_DUE. SCOPE displays a warning banner to the tenant.

Open the subscription in MIQ. Check the invoice list to confirm which invoice failed.

Click Setup Payment to resend the Stripe billing portal link, or Send Invoice to email a reminder.

Once the client pays, Stripe webhook fires and status returns to ACTIVE automatically.

Getting a Change Order Signed by a Client

Open the estimate or work order. Click the change order row you need signed.

Click Request Signature. Enter the client's email, customize the subject and message if needed, and submit.

The client receives an email with a one-time signing link. They click it, review the CO details, sign using their preferred method, and submit.

You receive a confirmation email. The signature appears on the CO detail with a full audit trail (IP, timestamp, method, SHA-256 hash).