Texas Web Service/Documentation
Getting Started

Core Concepts

TWS OS is the operational nervous system of your practice. It replaces the disconnected stack of CRMs, scheduling tools, billing software, and follow-up sequences with a single intelligent platform built specifically for Texas service businesses.

Why we call it an Operating System

Your laptop has an operating system that runs every app on top of it — managing memory, file storage, networking, and device I/O so you never have to think about it.

TWS OS does the same for your practice. It manages your contacts, your calendar, your messages, your invoices, and your reputation — and it connects them intelligently so they respond to each other in real time.

When a new lead fills out your contact form at 11 PM on a Friday, TWS OS reads the message, responds within 60 seconds, offers booking slots, generates a consultation invoice on confirmation, and schedules a Google review request for 48 hours later. No one at your practice touched a keyboard.

The core automation engine is constructed as an event-driven workflow system. Each automation consists of a Trigger, a network of Nodes connected in sequence or branching paths, and Connections that funnel structured data between them.

The Automation Lifecycle

1

Trigger

A form fill, booked appointment, inbound SMS, invoice event, or webhook initiates the run.

2

Validation

The contact payload is verified, merged with your CRM record, and scored for urgency and intent.

3

AI Routing

The AI intake node reads intent, drafts a contextual response, and selects the correct next node path.

4

Execution

System sends SMS/email, books the appointment, generates a Stripe invoice, and schedules review requests.

The Four Building Blocks

1. Workflows

A Workflow is a custom operational path for a specific business scenario. Each workflow handles a unique scope of work — for example:

  • →new-patient-onboarding — from first contact to confirmed appointment
  • →unpaid-invoice-chaser — automated payment reminders at 3, 7, and 14 days
  • →post-appointment-review — Google review request 48 hours after service
  • →hvac-emergency-dispatch — inbound SMS triage → technician routing → ETA confirmation

Workflows run asynchronously inside the TWS OS queue cluster so they can pause for external events (e.g., waiting for a payment, waiting for a booking confirmation) without blocking.

2. Triggers

Triggers listen for specific operational events at your practice. When an event fires, the trigger launches an execution of its workflow and appends the event payload as global context available to all downstream nodes.

Contact form submission
Appointment created
Appointment completed
Invoice paid
Invoice overdue
Inbound SMS received
Stripe webhook
Manual trigger

3. Nodes

Nodes are the individual action units in your workflow. Each node has a type, a config, and produces an output that downstream nodes can reference.

ai_agent_intake
AI Agent Intake
Reads the contact's message, extracts intent, urgency, and key entities. Routes to the appropriate action path.
send_sms
Send SMS
Delivers a context-rich text message via Twilio. Supports template variables from any upstream node output.
send_email
Send Email
Sends a personalized email via SendGrid. Subject, body, and attachments are all dynamically rendered.
appointment_booking
Appointment Booking
Creates a real appointment in Acuity or Google Calendar. Returns a booking confirmation URL.
stripe_invoice_generation
Stripe Invoice
Generates a Stripe invoice and routes payment directly to your connected Stripe account. TWS never holds funds.
google_review_request
Google Review Request
Sends a direct link to your Google Business review page via SMS at a configurable delay post-service.
wait
Wait
Suspends the workflow execution for a defined duration — e.g., "wait 48 hours" before the review request.
condition
Condition
Branches the workflow based on a boolean expression — e.g., "if lead_score > 70, send to booking; else, send nurture SMS".

4. Connections

Connections define how data flows between nodes. Use template variable syntax to pass fields from any upstream node output into a downstream node config:

// Reference AI intake output in the SMS body:
"body": "Hi {{ $node['AI_Intake'].output.first_name }}, thanks for reaching out about {{ $node['AI_Intake'].output.entities.service }}. We have availability on {{ $node['Booking'].output.confirmed_date }}."

// Reference invoice URL in follow-up email:
"body": "Your invoice is ready: {{ $node['Stripe_Invoice'].output.invoice_url }}"

How Texas Practices Use This

Dermatology
New patient inquiry at 11 PM
  1. 1.AI intake reads message
  2. 2.SMS response within 60s
  3. 3.Consult booking offered
  4. 4.Invoice on confirmation
  5. 5.Review request in 48h
Legal
Potential client submits contact form
  1. 1.AI reads case description
  2. 2.Intake call scheduled
  3. 3.Retainer invoice generated
  4. 4.Engagement letter sent
  5. 5.Onboarding sequence begins
HVAC
Emergency service request via SMS
  1. 1.Inbound SMS detected
  2. 2.AI triages urgency
  3. 3.Technician dispatch SMS sent
  4. 4.ETA confirmed to client
  5. 5.Job completion review requested
← AuthenticationWorkflow Builder →