OBD Ecosystem Overview

How OBD Premium tools are designed to work together — always with explicit control.

OBD Premium is a suite of focused tools designed to work together without automation surprises. Each connection is explicit, draft-first, and business-controlled.

Key idea: when one tool “connects” to another, it means a deliberate export/import, an explicit approval step, or a controlled mapping—never hidden automation.

Ecosystem map

A conceptual view of how the apps relate. Lines illustrate intent and information flow—not automatic execution.

AI FAQ Generator

Turn approved content into customer-ready FAQs that can be reviewed and exported.

AI Content Writer

Draft-first copy generation that stays aligned with your brand voice and goals.

Scheduler & Booking

Bookings and appointment context, designed to stay tenant-safe and explicit.

Social Auto-Poster

Queue + approval-driven publishing—no silent background posting.

Brand Kit

A single source of truth for colors, voice, and reusable brand assets.

AI Help Desk

Knowledge + answers with explicit imports and review-first handling.

CRM

Contacts and history that can inform scheduling and review outreach—explicitly.

Review Request Automation

Request flows that stay business-controlled and never cross tenants.

Apply-onlyDraft-firstManual linking

On mobile, the map collapses to cards-first for readability; the relationships are fully described below.

How the relationships work (conceptually)

Brand Kit as the source of truth

Brand Kit establishes your reusable foundation (voice, tone cues, colors, and core assets). Other apps can reference that foundation through explicit import/apply steps—so brand changes never “silently” rewrite live content.

Content Writer supports downstream drafts

The Content Writer produces drafts you can reuse for FAQs, social posts, and help desk knowledge—but reuse is always controlled (copy/export/import), never automatic publishing.

Scheduler, CRM, and review requests stay explicit

Scheduler and CRM can share context conceptually (contacts, appointment history, outcomes), and Review Requests can be informed by CRM—but all flows are designed to be tenant-safe and business-controlled, with no cross-business visibility.

Help Desk + FAQ Generator are a deliberate knowledge loop

Help Desk content can be curated into FAQs (and FAQs can be imported back as knowledge), but only through explicit approval. This avoids “AI changed my site” surprises.

What OBD does not do

No automatic publishing
No background automation
No cross-business data sharing
No AI actions without approval