Skip to content
Tech360 logo

AI Agent Communication Pipeline

From the first SMS to final delivery — on record, every step.

Tech360 runs one transparent, eleven-stage journey: Client ID, exact replies, saved messages, admin gates, HTML preview, confirmed payment and a documented handover. You always know what happens next.

BrandTech360
Public webchatAI agent
Client IDTECH-2026-000001
Channels saved10 channels
Start your project Explore all 11 stages

HTML Preview Before Payment. Source Code After Full Payment.

One identity · one record

Every conversation begins with the same verified identity.

The AI agent creates a Client ID, opens a client profile and attaches every message to it — from the first SMS to the final review request. Nothing lives in an inbox that the CRM cannot see.

Websitebdtech360.com
Official emailinfo@bdtech360.com
Public webchatAI agent
Client ID formatTECH-YYYY-NNNNNN

The non-negotiable rule

HTML Preview Before Payment. Source Code After Full Payment.

An HTML/demo preview is for review. Final source code, full files, admin access and deployment handover are released only after payment is confirmed and an admin approves the handover.

Enforced in code, not just words

Omnichannel intake

Ten channels. One client profile.

Every WhatsApp, SMS, email, website form, Facebook, Instagram, LinkedIn, X, Messenger and manual admin message is saved under the client profile and its Client ID.

WhatsApp

Inbound messages and outbound WhatsApp replies

Saved in CRM

SMS

First-SMS intake and SMS replies

Saved in CRM

Email

Inbound mail and exact email subjects/bodies

Saved in CRM

Website form

Consent-evidenced contact form enquiries

Saved in CRM

Facebook

Page messages relayed into the CRM

Saved in CRM

Instagram

Direct messages relayed into the CRM

Saved in CRM

LinkedIn

InMail and page messages relayed into the CRM

Saved in CRM

X

Posts and direct messages relayed into the CRM

Saved in CRM

Messenger

Conversation messages relayed into the CRM

Saved in CRM

Manual admin message

Operator-composed messages, always logged

Saved in CRM

Source detection → Client ID → saved inbound → first reply. Webhooks are fail-closed and idempotent; unverified identity claims are never merged into an existing client.

See our process

The always-save contract

The AI creates the profile — and never stops writing to it.

Incoming and outgoing messages, all channel bodies, the Client ID, every status change and timestamp, admin approvals, payment proof and delivery proof.

The client profile

Created at first contact · keyed by TECH-2026-000001

  • Client ID
  • Client name
  • Business name
  • Business type
  • Phone
  • WhatsApp
  • Email
  • Lead source
  • Message history
  • Scope history
  • Approval history
  • Payment history
  • Delivery history
  • Review history

AI must always save

No message without a record, no record without a timestamp

  1. 1Incoming message
  2. 2Outgoing message
  3. 3Email body
  4. 4WhatsApp body
  5. 5SMS body
  6. 6Client ID
  7. 7Status change
  8. 8Timestamp
  9. 9Admin approval
  10. 10Payment proof
  11. 11Delivery proof

The client profile is private. This public page shows the contract, never a real client record.

The 11-stage journey

Read the exact message for every stage.

Select a stage to see the AI's action, its WhatsApp/SMS reply, the email subject and body, the CRM fields it saves, and whether an admin must approve it first.

1

Stage 1 · FIRST MESSAGE

First SMS / first message received

AI may auto-send

AI action

  • Create lead in CRM.
  • Generate Client ID.
  • Save incoming message.
  • Detect source.
  • Ask for business type and project need.
WhatsApp / SMS reply
Hi, thank you for contacting Tech360.

Your inquiry has been received and your Client ID is:

[CLIENT_ID]

Tech360 helps business owners build websites, eCommerce systems, CRM software, ERP, WhatsApp automation, n8n workflows, AI systems, dashboards, and business automation.

To suggest the right solution, please reply with:

1. Your business type
2. Business name
3. What problem do you want to solve?
4. Do you need website, CRM, eCommerce, automation, or full system?
5. Existing website or Facebook page link, if available
6. Expected launch timeline

After receiving this, our AI system will prepare your recommended plan.
Email · Tech360 Inquiry Received - Client ID [CLIENT_ID]
Subject: Tech360 Inquiry Received - Client ID [CLIENT_ID]

Dear [CLIENT_NAME],

Thank you for contacting Tech360.

Your inquiry has been received and your Client ID is:

[CLIENT_ID]

Tech360 helps businesses build premium websites, CRM systems, eCommerce platforms, WhatsApp automation, n8n workflows, dashboards, AI systems, and business automation solutions.

To prepare the right recommendation, please share:

1. Your business type
2. Business name
3. Main business problem
4. Required system: website, CRM, eCommerce, automation, or full system
5. Existing website/Facebook page link, if available
6. Expected launch timeline

Once we receive the information, our system will prepare your recommended digital plan.

Best regards,
Tech360 Team
Website: https://bdtech360.com
Email: info@bdtech360.com

CRM saves

status = New Leadclient_id = [CLIENT_ID]lead_source = [SOURCE]communication_log = savednext_action = Wait for business type
Stage 1 of 11

Auto-send vs admin approval

The AI is helpful — and deliberately not authorised to do everything.

Auto-send is an allowlist. Everything else fails closed: an unknown stage or an amount, invoice, legal, dispute or delivery-link marker requires an admin decision first.

AI can auto-send

9 explicitly allowed messages

  1. 1First reply
  2. 2Business type request
  3. 3Recommended plan
  4. 4Scope questions
  5. 5Meeting link
  6. 6HTML preview notification
  7. 7Revision acknowledgement
  8. 8Payment received acknowledgement
  9. 9Review request

Admin approval required

7 hard gates before anything is sent

  • Final Scope of Work
  • Payment instruction with amount
  • Invoice
  • Legal/refund response
  • Source-code handover
  • Final delivery file links
  • Dispute response

Final rules

  • No source code before payment confirmation.
  • No final legal message without admin approval.
  • No payment-specific message without admin approval.
  • No sensitive files in public AI content.
  • HTML Preview Before Payment.
  • Source Code After Full Payment.

The sender refuses to release source code before confirmed payment, never publishes sensitive files in client-facing content, redacts phone numbers from AI-generated copy, and records an audit event for every status change and approval decision.

The delivery promise

Two gates, in this order. No exceptions.

The rule is visible on the website, present in every relevant message, enforced by the send layer and re-checked before any file is released.

HTML Preview Before Payment

After the Scope of Work is approved, an HTML/demo preview is shared so you can review the design, structure and project direction. A preview link is harmless: it contains no source code, no credentials and no deployable files. The client replies Approved, Need revision or Need meeting.

Preview notification is auto-sent · tracked with preview_sent_date

Source Code After Full Payment

Payment is confirmed and recorded, then final delivery is prepared. The delivery notice is sent, but the actual file links, source code, admin access and deployment handover are released only after an admin approves the handover. After delivery the client confirms receipt and a password change.

admin_approval_required_for_file_release = yes · delivery proof saved

Payment-specific messages are never improvised. An amount, invoice or payment instruction is created by an admin-approved action; the AI only acknowledges a payment that has already been recorded.

Read the terms

Start at stage one

Send the first message. Watch the whole pipeline begin.

This form posts to the real consent-gated intake API. On success the CRM creates your Client ID and stores the enquiry; the AI agent follows up with the exact Stage 1 reply shown above.

  • Explicit consent and a request ID are required — no silent opt-ins.
  • Your message is saved under a new Client ID, never merged on an unverified claim.
  • No payment is due at this stage. Scope, preview and pricing come later.
  • Never send passwords, API keys or payment-card codes through this form.
Track an existing project

0/20 minimum

Or email info@bdtech360.com

Everything connected

One pipeline, one website, one source of truth.

Client portal

Sign in with your Client ID to see status, approvals and delivery history.

Open

How we work

The seven-phase production process behind every approved Scope of Work.

Open

Scope & policy

Read the terms, privacy policy and payment/handover terms in one place.

Open

Reviews & referrals

Stage 11 closes the project with a review request and an optional recommendation.

Open

About this copy: this page shows the approved master wording. The live sender adds consent and legal clarifications to the same messages, and the enforced auto-send / admin gates are checked before anything leaves the CRM. The read-only API at /api/pipeline/public exposes this same contract without any client data.

Next step

Ready to start at stage one?

Send one enquiry. We will create your Client ID, save every message, share a preview before payment and hand over source code only after full payment.

Start Your Project

Every engagement is on-record: Client ID, written scope, verified payments, full handover.