ag/audeExplore the OS ↗
THE COMPLETE DESIGN INVENTORY

Every team.
Every handoff.

The OS workflows we designed, with the AGLAUDE SaaS additions kept separate.

Design scope, not a production availability guarantee. Provider setup, migrations and release validation determine what is available. All product examples use fictional data.

Lead → call → sale → QA → human assignment → delivery → reporting → retention

Client lifecycle and ownership

  • Lead capture → cold-rep qualification → closer follow-up → sale/order → QA verification → human assignment → CDT delivery → client reporting and retention.
  • Order and campaign drafts; close-sale workflow; activation-call flow; client status transitions and a visible handoff history.
  • Sales-owned activation and an authorized Sales Manager handoff to delivery; bad-signup classification after a refund, kept distinct from ordinary churn.
  • Client records, contacts, packages, monthly charges, ownership, files, timelines, tasks, tickets and communication history.

Cold-rep leads and dialer

  • Dedicated cold-rep telephonic dialer and queue; manual dialing; softphone connection on initial use rather than a second click.
  • Personal leads list; CSV import and downloadable sample; imported leads may stay personal instead of automatically entering the dial queue.
  • Call any saved lead; reuse the previous outgoing number where permitted or choose an assigned number.
  • Uncluttered disposition form with “Take next call”; break and coaching controls; persistent records with coaching status separate from dialer state.
  • Cold reps alone use the dedicated sales dialer. Eligible other roles use Phone.
  • Cold-agent access ruling: AI Agent, AI Library and Follow-ups available; AI Studio, Connectors navigation and MCP access excluded.

Follow-ups, calendars and alerts

  • Appointment set, interested, follow-up, callback requested and busy/call-later outcomes offer scheduling.
  • Internal follow-up calendar, AI-assisted follow-up creation, reminders, and personal follow-up lists for cold reps and closers.
  • Saved auto-dial and manual-dial leads populate the owning rep’s OS; scheduled work retains the associated lead and client context.
  • Follow-up notifications appear in the Dynamic Island; client-local time helps teams contact people at suitable times.

Sales management and targets

  • Cold-agent and closer profiles; signup counts, closed monthly revenue, closing ratios, transfer events and QA history.
  • Closer or sales-supervisor signup targets for assigned cold reps; closer signup targets roll up from those reps.
  • Sales Manager visibility across individual reps, closers, teams and the entire floor; daily, weekly and monthly target views.
  • Role-scoped revenue visibility enforced by the API; agents and closers see their own figures.
  • Current-month signup upsell revenue for Sales Managers; daily bounties and rush-hour incentives in the broader design scope.

Quality assurance

  • Incoming calls, call transcripts, QA queue, review screens and ledgers; separate sales and delivery worklists.
  • Versioned rubrics, evidence-backed scoring, manual score/override paths, disagreements and review history.
  • Deterministic fatal rules and escalation; call-duration gates; department trend taxonomy and trend comparisons.
  • Rapport scoring, client-health signals, coaching records and feedback into AI training.
  • Reconciliation of expected meetings/calls and captured evidence; missing or incomplete sources must remain visible.

Assignment and reassignment

  • Human assignment gate after sale and QA; choose a delivery rep using capacity/load, liable revenue and QA scores.
  • QA proposes reassignment when a rep leaves or changes role; client list shows “Pending CDT Manager approval”.
  • CDT Manager approves or rejects. Following approval, the designed workflow completes the transfer automatically.
  • Keep client data and files with the record; include unfinished tasks and open tickets in the approved ownership-transfer workflow.
  • Audit the previous owner, new owner, requester and decision; protect against stale or unauthorized transfers.

Delivery, tasks and support

  • Role-scoped client book and client workspaces; delivery organisation and team oversight.
  • Customer and delivery statuses, on-hold request/approval flow, cancellations and exception handling.
  • Dashboard as a measured task list: delivery work, extracted commitments, assigned tasks and manually added tasks.
  • Task completion, dismiss-with-reason, due dates, overdue work, manager assignment and on-time performance scores.
  • Client support tickets, disputes, escalation paths, client-health reviews and continuity through rep transfers.

Phone and external messaging

  • A separate, easy-to-use Phone workspace for eligible non-cold-rep users, with Apple-inspired messaging and call controls.
  • Linq messaging design for iMessage, RCS and SMS; actual available channel, delivery/read state, media and line health depend on provider support.
  • Voice is handled by a separate supported provider such as Telnyx; Linq inbound forwarding and outbound caller identity require verified configuration. Linq is not a native voice API.
  • Client Text and Call buttons route into the correct workspace with the assigned CDT rep’s eligible number.
  • Admins assign numbers to users and grant messaging only, calling only or both; enforce those permissions server-side.
  • Phone management, provider-number inventory, and number purchasing where each provider supports it. No assumed Linq purchasing capability or automatic purchase authorization.
  • Number-to-rep attribution, call events, recording/transcription/dispositions, message history, verified webhooks and duplicate/retry handling.

Internal team chat

  • Direct messages and groups; recipient search separate from OS-wide search; conversation search and history.
  • File attachments, clickable links, emoji picker, message replies and iMessage-style reactions.
  • Profile photos, preset avatars and initials; member-scoped private conversations.
  • Unread state, read acknowledgements and chat notifications in the Dynamic Island instead of relying on the top-right bell.
  • Group approval/denial where policy requires it. Private team chat is not a source for AI analysis.

AI and knowledge

  • Permission-bound agent runtime and tool registry; section-scoped Ask Claude; client and workflow context.
  • Reads and drafts within the user’s permissions; human confirmation for client-facing messages or consequential changes.
  • Suggestions for upsells, at-risk clients and missed commitments; commitment extraction and reminders.
  • Shared AI library, reusable knowledge, AI training and QA-feedback loop; role/user AI switches.
  • AI Studio for eligible roles; authorized MCP/connector access. Cold reps get no MCP.
  • Action audit, bounded usage and cost-aware model/tool selection; the model does not independently impose deterministic business consequences.

Reporting and management visibility

  • OS entry points to the separate client-report generator; report generation status, authorized PDF and share links.
  • Organisation, department, team, closer and individual reporting; role-appropriate revenue and target visibility.
  • Biweekly/monthly reporting, department trends, QA averages, fatal ledgers and unhappy-client signals.
  • Client/business-level double-count protection across activations; distinguish bad signups, refunds and normal cancellations.
  • Chargeback, refund, unauthorized-charge and overcharge reporting linked to underlying transactions where integrated.

Billing and commercial controls

  • Monthly recurring charge visibility and authorized edits, packages and revenue reporting.
  • Designed payment authorization, capture/refund permissions, recurring subscriptions, billing-date changes and decline/dunning workflows.
  • Merchant reconciliation: authorized versus actually charged amounts, overcharges and refund history.
  • NMI card capture remains parked under the latest recorded scope. Designed billing functionality is not a claim that live payment collection is enabled.

Staff, HR and administration

  • Staff invitation, editing incorrect names/emails, role changes/promotions, staff-specific search and team assignment.
  • Admin/Super Admin permission editor with server-enforced capability and scope rules.
  • Only Super Admin may change the Admin role’s permission set; Admin cannot edit Super Admin grants.
  • Super Admin console, staff/admin roster, worklog, settings, customer-status configuration and custom-field/visibility configuration in the design scope.
  • Hiring pipeline, candidate imports, department hiring targets, attendance, announcements and resource/seat tracking.
  • Working/billable hours, shifts, breaks and approved corrections are part of the broader backlog. Chrome integration was mentioned but remains undefined.

Authentication, security and audit

  • Passwordless authentication, session handling, role-specific access and route protection; specialised cold-rep login/session policy.
  • IP allowlist management. Super Admin is the only network exemption and requires MFA; all other roles are intended to require approved networks once enforcement is enabled.
  • TOTP enrolment/recovery, honest MFA errors, and explicit rollout order to avoid lockout.
  • Security readiness: trusted request address, allowlist membership, enforcement mode and current authentication assurance.
  • Server-side authorization, database-level scope/RLS/grants, audited refusals and audit history.
  • Protected credentials and vendor-key handling; signed trusted proxy headers, webhook verification, validation, rate limits and idempotency.

Integrations and reliability

  • Linq messaging, Telnyx voice, Gmail, Google Calendar and Granola; client timelines combine permitted external communication.
  • Admin connector policies with per-role and per-user controls; each user sees only available integrations.
  • Client-only email history/backfill; roster-scoped Google access; calendar/meeting reconciliation and scheduled Granola ingestion.
  • Client GBP authorization and per-client Drive folders remain dependent on external setup; the report generator stays a separate system.
  • Ingestion ordering, retries, replay, deduplication and visible failure recovery; number/email/meeting-owner attribution to the responsible rep.
  • Deployment/build checks, API tests, observability, dependency review and service-continuity checks. Migrations must be explicitly verified rather than assumed applied.

UI and operational experience

  • Apple/macOS visual language, Liquid Glass controls, green enabled/toggled states and responsive navigation.
  • Dynamic Island for timely chat and follow-up signals; accessible focus and keyboard interactions.
  • Clear search within the workflow, uncluttered forms, meaningful empty/error states and removal of developer notes from ordinary user screens.
  • A consistent client journey without forcing teams to switch across external applications.

AGLAUDE SaaS proposals — additional scope

  • Isolated agency tenants, provisioning, custom domains and full white-label branding.
  • Configurable service packages, workflows, role templates and reusable agency blueprints.
  • Branded client portals for requests, approvals, files and progress.
  • Client profitability, delivery capacity, scope-creep detection and forecasting.
  • Usage budgets, AI/communications cost visibility, subscriptions and optional rebilling. These are proposed SaaS additions, not verified current OS capabilities.