Templates / Workflow Library

What templates cover

OrcaPulse includes a full template layer that spans workflow configurations and individual message content. The system provides pre-built sample workflows for fast onboarding, dedicated template models for email, SMS, and WhatsApp messages, and AI-powered generation to create or improve templates from a description.

Templates in OrcaPulse are not static files. They are structured records with variable support, category metadata, status tracking, and direct linkage to workflow steps. This means teams can build once and reuse across multiple workflows and campaigns.

Workflow templates

Workflows in OrcaPulse are built from ordered steps, where each step can be an SMS message, email, WhatsApp message, AI-powered call, wait timer, CRM sync, or webhook action. A workflow also carries scheduling configuration, recall settings, inbound call handling, and day/night mode behavior.

Workflow statuses include Draft, Active, Paused, and Archived, which gives teams a lifecycle for managing configurations from creation through to retirement. The workflow controller supports full CRUD operations plus testing and simulation, so templates can be validated before going live.

• Seven step types: SMS, Email, WhatsApp, AI Call, Wait, CRM Sync, and Webhook steps can be configured in any order.
• Status lifecycle: workflows move through Draft → Active → Paused → Archived, with status changes managed via a dedicated endpoint.
• Test before launch: the workflow test endpoint lets teams simulate execution against sample data before activating.

Sample workflow picker

OrcaPulse ships with ten pre-built sample workflows designed for common use cases. Each sample includes a full step configuration, pre-written email and SMS template content, AI assistant prompt and voice settings, and scheduling defaults. Teams can select a sample during onboarding to get a working workflow instantly.

• Full configuration: each sample includes step definitions, template content, AI assistant settings, and voice configuration.
• Instant activation: samples are designed to be usable immediately after selection without requiring manual configuration.
• Customizable base: after selecting a sample, teams can modify any step, template, or setting to fit their specific needs.

Email templates

Email templates in OrcaPulse are stored records with a name, subject line, HTML body, and plain-text body. The system automatically extracts variables from the template content using the {{variableName}} syntax, so templates can be personalized at send time with lead data.

Templates are categorized as marketing, transactional, notification, or other, which helps teams organize their library as it grows. The email template controller supports full CRUD operations plus a direct send endpoint with idempotency protection against duplicate rapid sends.

• Variable extraction: variables like {{name}}, {{email}}, and {{company}} are automatically detected from template content.
• Categories: marketing, transactional, notification, and other categories keep the template library organized.
• Direct send: templates can be sent standalone via the send endpoint, not only through workflow steps.
• Deduplication: idempotency keys prevent accidental duplicate sends during rapid operations.

SMS templates

SMS templates use a lightweight structure with a name, content body, and extracted variables. The system supports status toggling so teams can activate or deactivate templates without deleting them. All templates are user-scoped, meaning each account manages its own library independently.

The SMS template service handles CRUD operations with user-scoped access control, validation on creation, and a toggle endpoint for quick enable and disable actions. This makes it straightforward to manage a growing library of message templates across different campaigns.

• Status toggle: templates can be switched between active and inactive states without deletion.
• User-scoped: each user manages their own SMS template library with independent access control.
• Variable support: SMS content supports the same variable interpolation as email templates.

WhatsApp message templates

WhatsApp templates in OrcaPulse integrate with the Twilio Content API using content SID references. Templates follow WhatsApp naming conventions with lowercase underscore formatting and move through a status lifecycle: draft, pending approval, approved, rejected, and deleted.

Each template is categorized as Marketing, Utility, or Authentication, matching the WhatsApp Business API requirements. Templates can include headers, footers, and interactive buttons. The system also tracks usage statistics including send count and last-used timestamp.

• Approval workflow: WhatsApp templates move through draft → pending approval → approved before they can be used in live sends.
• Business API categories: Marketing, Utility, and Authentication categories match WhatsApp platform requirements.
• Rich content: templates support headers, footers, and interactive button components beyond plain text.
• Usage tracking: each template tracks how many times it has been used and when it was last sent.

AI template generation

OrcaPulse includes an AI template generation layer that can create new SMS and email templates from a purpose description and tone specification, or improve existing template content. The generation service uses OpenAI and integrates with the platform credit system.

This means teams do not need to write every template from scratch. They can describe what the message should accomplish, choose a tone, and receive a production-ready template that they can then edit and attach to workflow steps.

• Generate SMS: provide a purpose and tone to receive a ready-to-use SMS template.
• Generate email: specify requirements and receive a complete email template with subject line and body.
• Improve existing: submit a current template to get AI-suggested improvements for clarity, engagement, or conversion.
• Credit-based: template generation consumes platform credits, keeping usage aligned with account plans.

How templates connect to workflows

Templates are not isolated assets. They are directly linked to workflow steps. When building a workflow, each SMS step can reference an SMS template, each email step can reference an email template, and WhatsApp steps use approved WhatsApp templates via content SID. AI call steps reference assistant configurations with their own prompt and voice settings.

This connection means changes to a template can affect every workflow that references it. The workflow builder in the frontend provides a visual interface where teams can configure steps, attach templates, set scheduling, and manage assistant assignments all in one place.

• Step-template binding: each workflow step type references the appropriate template type for its channel.
• Assistant linking: AI call steps bind to assistant configurations with prompt, voice, and behavior settings.
• Visual builder: the workflow builder provides drag-and-drop step management with inline template configuration.
• Scheduling integration: templates execute within the workflow scheduling context including timezone, day/night mode, and recall settings.

Current project shape

The template system is well-structured and production-ready for individual template types and the sample workflow picker. The platform already supports full CRUD for email, SMS, and WhatsApp templates, AI-powered generation, and ten pre-built workflow samples.

What the project does not yet include is a shared workflow library with cloning or duplication, cross-user template sharing, workflow versioning or rollback, or a public template marketplace. Today, templates and workflows are user-scoped and the sample picker serves as the primary library experience.

Next steps

After Templates / Workflow Library, the next useful Operations page is Security, which documents the authentication, encryption, and protection mechanisms across the platform.