Firetip | Unified Communications Infrastructure

Getting Started

Overview

Firetip is the communications and dispatch platform. Faigen provides the intelligence layer that can operate on top of Firetip's communication workflows.

The purpose of this separation is straightforward: AI should improve communication without becoming the communications infrastructure itself.

Firetip continues to control identity, audiences, permissions, campaign state, channel selection, dispatch, delivery tracking and operational workflow. Faigen provides intelligence for the content and decision-making stages where AI assistance is enabled.

Core integration principle

Faigen enhances Firetip. It does not bypass Firetip's authentication, audience controls, campaign permissions or dispatch pipeline.

AI Translation

Transform campaign content into supported target languages while retaining Firetip's campaign and dispatch context.

Content Intelligence

Assist with campaign copy, subject lines, tone, structure and alternative content.

Optimisation

Analyse existing communication content and produce improved or alternative versions.

Automation Intelligence

Allow AI-assisted actions to participate in Firetip automation workflows.

Getting Started

Quick Start

A Firetip + Faigen workflow normally follows four stages: configure the integration, prepare the communication, process the content and dispatch through Firetip.

Confirm that the Firetip account is authorised to use AI features.

Configure the Faigen connector and its server-side credentials.

Create or select the Firetip campaign, automation or communication.

Select the required AI operation.

Validate the returned content before production dispatch where human review is enabled.

Allow Firetip to retain ownership of the final dispatch operation.

Recommended production model

AI output should normally enter a Firetip review or validation stage before being committed to production communication.

System Design

Architecture

The Firetip + Faigen architecture separates the communication control plane from the AI intelligence plane.

1

Identity

Domains, sender identity and communication infrastructure.

2

Audience

Contacts, lists, segmentation and recipient context.

3

Firetip

Campaigns, permissions, workflows and channel orchestration.

4

Faigen

AI processing, translation, optimisation and content intelligence.

5

Dispatch

Firetip sends the resulting communication through the selected channel.

Campaign

Original communication

Faigen

AI processing

Review

Validate result

Dispatch

Firetip delivery

AI Features

Capabilities

Individual AI capabilities can be exposed through Firetip's campaign editor, automation engine or other authorised communication workflows.

Capability	Purpose	Typical Firetip Stage	Human Review
Translation	Convert communication into another language.	Pre-dispatch	Recommended
Copy Assistance	Generate or refine communication content.	Campaign creation	Recommended
Optimisation	Improve existing messaging.	Campaign editing	Recommended
Personalisation	Adapt communication using approved audience context.	Content preparation	Depends on workflow
Automation AI	Perform AI-assisted actions after workflow triggers.	Automation	Depends on workflow

Integration

Integration Model

Faigen should be invoked from Firetip's server-side integration layer. Browser JavaScript should communicate with Firetip rather than directly exposing AI service credentials.

FIRETIP AI PIPELINE

Campaign / Automation
    |
    v


Firetip AI Request
|
v
Faigen Connector
|
+---- Translation
|
+---- Optimisation
|
+---- Content Assistance
|
+---- Personalisation
|
v
Firetip Validation / Review
|
v
Firetip Campaign Engine
|
+---- Email
+---- SMS
+---- WhatsApp
+---- API
|
v
Recipient / External System

Server-side integration

Keep connector credentials, authentication logic and AI service communication on the Firetip server. Do not place private credentials inside campaign HTML or browser-side JavaScript.

Campaigns

Campaign AI

Campaign AI allows Faigen to operate between campaign creation and final Firetip dispatch.

Standard campaign lifecycle

CAMPAIGN LIFECYCLE

User creates campaign


Firetip loads campaign content
User selects an AI operation
Firetip sends an authorised request
Faigen processes the request
Firetip receives the result
User reviews or validates the result
Campaign is saved
Firetip queues the communication
Firetip dispatches through the selected channel

Human approval

AI output should be treated as generated communication content rather than automatically trusted production content. Firetip can retain a review stage before dispatch.

AI Features

Translation

Firetip can use Faigen as the language intelligence layer for multilingual communications.

Translation flow

TRANSLATION

Original Campaign
    |
    v


Select Target Language
|
v
Firetip AI Request
|
v
Faigen Translation
|
v
Translated Content
|
v
Review / Validation
|
v
Firetip Dispatch

Conceptual request

JSON / CONCEPTUAL

{
"operation": "translate",
"source_language": "en",
"target_language": "fr",
"content": {
    "subject": "Your account is ready",
    "body": "Welcome to our service."
},
"context": {
    "channel": "email"
}


}

The structure above is a conceptual Firetip integration example. The production connector should use the exact endpoint, authentication mechanism and schema configured for the connected Faigen service.

Translate before final dispatch

Translation should normally happen before Firetip queues the final communication so the resulting content can be reviewed, tracked and dispatched as normal Firetip content.

AI Features

Content Optimisation

Faigen can assist with improving communication content while Firetip remains responsible for delivery and campaign execution.

Subject Lines

Generate or refine alternative subject lines.

Copy Refinement

Improve clarity, structure and communication tone.

Audience Adaptation

Adapt approved content for audience segments.

Variations

Produce alternative versions of a communication.

Example optimisation lifecycle

OPTIMISATION

Existing Campaign
    |
    v


Select Optimisation
|
v
Faigen Analysis
|
v
Generated Variation
|
v
User Review
|
v
Save Approved Version
|
v
Firetip Dispatch

AI Features

Personalisation

Faigen can assist with audience-aware communication when Firetip supplies an approved set of recipient context.

Personalisation should be constrained to information that Firetip is authorised to use for the specific communication workflow.

Example context

CONCEPTUAL CONTEXT

{
"recipient": {
    "first_name": "Alex",
    "language": "en",
    "segment": "customer"
},
"communication": {
    "channel": "email",
    "purpose": "account_update"
}


}

Minimise unnecessary recipient data

Only provide the AI workflow with recipient context that is necessary for the requested operation. Avoid sending unrelated account, authentication or sensitive information.

Automation

AI Automations

Faigen actions can participate in Firetip automation workflows where the account configuration and workflow permissions allow them.

AUTOMATION PIPELINE

Trigger
    |
    v


Firetip Automation
|
v
Validate Conditions
|
v
Faigen AI Action
|
+---- Generate
|
+---- Translate
|
+---- Optimise
|
v
Validate Result
|
v
Channel Selection
|
v
Firetip Dispatch

Automation safety rules

Validate the automation trigger before invoking AI.
Apply account and workflow permissions before processing.
Preserve the original content if AI processing fails.
Prevent repeated AI invocation when a workflow loops.
Record enough execution information to diagnose failures without logging secrets.

Developer Integration

API Contract

Firetip's Faigen connector should be treated as the integration boundary between the Firetip application and the AI service.

Conceptual API examples

The examples in this section describe the Firetip integration contract and are not intended to invent or replace the production Faigen endpoint, authentication or request schema.

POST /configured-faigen-operation CONNECTOR

The actual production endpoint is supplied by the configured Firetip Faigen connector.

Conceptual request

JSON

{
"action": "optimise",
"request_id": "firetip-generated-id",
"content": {
    "subject": "Your campaign subject",
    "body": "Your campaign content"
},
"context": {
    "channel": "email",
    "audience": "customers"
}


}

Conceptual response

JSON

{
"success": true,
"request_id": "firetip-generated-id",
"action": "optimise",
"result": {
    "subject": "Improved campaign subject",
    "body": "Improved campaign content"
}


}

Recommended request metadata

Field	Purpose	Required
action	Identifies the requested AI operation.	Yes
request_id	Allows Firetip to correlate requests, responses and failures.	Recommended
content	The communication content being processed.	Depends on action
context	Approved communication context.	Depends on action

Developer Integration

PHP Integration Pattern

Firetip integrations should be performed server-side. A PHP connector can follow the pattern below.

PHP

<?php


$payload = array(


'action' => 'optimise',

'request_id' => $requestId,

'content' => array(

    'subject' => $subject,

    'body' => $body

),

'context' => array(

    'channel' => 'email',

    'audience' => 'customers'

)


);

| /*                                                                         |
| -------------------------------------------------------------------------- |
| Send the payload through the configured Firetip/Faigen                     |
| connector.                                                                 |
| -------------------------------------------------------------------------- |
|                                                                            |
| The connector owns:                                                        |
|                                                                            |
| - endpoint configuration                                                   |
| - authentication                                                           |
| - transport                                                                |
| - timeout handling                                                         |
| - response parsing                                                         |
| - error handling                                                           |
|                                                                            |
| -------------------------------------------------------------------------- |
| */                                                                         |

$response = $faigenClient->process($payload);

if (
!empty($response['success']) &&
!empty($response['result'])
) {


$subject =
    isset($response['result']['subject'])
        ? $response['result']['subject']
        : $subject;

$body =
    isset($response['result']['body'])
        ? $response['result']['body']
        : $body;


}

| /*                                                                         |
| -------------------------------------------------------------------------- |
| If processing fails, preserve the original content.                        |
| -------------------------------------------------------------------------- |
| */

|

Credentials stay server-side

API keys, tokens and connector secrets should never be inserted into campaign HTML, public JavaScript or browser-visible configuration.

Developer Integration

Responses & Processing

Firetip should treat an AI response as untrusted application data until it has passed the appropriate validation and workflow checks.

Stage	Firetip Action
Transport	Confirm the request completed successfully.
Authentication	Confirm the connector accepted the request.
Parsing	Validate that the response is structurally usable.
Content	Confirm required fields are present and non-empty.
Workflow	Apply Firetip permissions and campaign rules.
Dispatch	Only approved content enters the normal Firetip dispatch pipeline.

Operations

Security

Keep Faigen credentials on the Firetip server.

Never expose private AI credentials in browser JavaScript.

Authenticate the Firetip user before allowing AI operations.

Validate campaign ownership and permissions.

Sanitise user-supplied campaign content.

Avoid logging credentials or sensitive payloads.

Use separate development and production credentials where supported.

Restrict AI operations to authorised workflows.

Firetip remains the control plane

Faigen should enhance Firetip's communication workflows rather than bypass Firetip's identity, audience, permission or dispatch controls.

Operations

Error Handling

AI processing should fail safely. A temporary AI failure should not silently destroy or replace the original Firetip communication.

Condition	Recommended Firetip Behaviour
Authentication failure	Stop the AI request and report a connector configuration error.
Service unavailable	Preserve the original content and report the AI operation as unavailable.
Timeout	Fail safely and preserve the original request.
Invalid response	Reject the result rather than overwriting the original content.
Empty AI result	Preserve the original campaign content.
Validation failure	Return the result to the review/error state rather than dispatching it.

Operations

Troubleshooting

AI action is unavailable

Check whether the Faigen connector is configured, authorised and enabled for the current Firetip account and workflow.

Request times out

Check connector timeout settings, service reachability and request size. The original Firetip content should remain intact when the AI request fails.

AI result is empty

Treat an empty result as an unsuccessful AI operation. Do not overwrite existing campaign content with an empty value.

Translation is incorrect

Review the source content, requested target language, campaign context and any terminology instructions being supplied by the configured AI workflow.

Campaign will not dispatch

Check the normal Firetip campaign validation and dispatch pipeline. AI processing should not bypass sender identity, audience, permissions or delivery requirements.

Operations

Best Practices

Review Before Dispatch

Keep human approval available for generated production communication.

Minimise Context

Send only the information necessary for the requested AI operation.

Use Timeouts

Never allow an AI request to block a Firetip workflow indefinitely.

Preserve Originals

Always retain the original communication until the AI result has been validated.

Production checklist

Connector configured

Credentials secured

User permissions enforced

Request validation enabled

Response validation enabled

Timeout handling enabled

Original content preserved

Dispatch remains under Firetip control

Operations

Integration Status

Faigen is exposed within Firetip as an AI intelligence layer. Individual actions and capabilities depend on the capabilities enabled by the connected configuration and the Firetip workflow using them.

AI Integration

Faigen provides the intelligence layer for authorised Firetip workflows.

Firetip Control Plane

Firetip remains responsible for communication infrastructure and dispatch.

FIRETIP AI INTEGRATION