Owner setup recipe

CRM & workflow setup

The working app is delivered above. This is the exact setup recipe for the CRM pipeline, custom fields, intake trigger, workflows, calendars, suppression rules, permissions and message templates — all inactive until Anil approves launch, sender identities, templates, cadence and channels. Building a database and drawing a workflow do not prove CRM synchronization or message delivery.

No production test messages, real client invitations, marketing, bookings or public publishing occur while building. Use authorized test records; otherwise mark execution "Not verified". Never display fake "connected", "registered", "submitted" or "workflow active" states.

CRM intake connection

Wired — inactive (launch not approved)
Form-tracking integration connected. No event fires until Anil approves launch.
Form slug
ditc-sourcing-inquiry
Form name
DITC Sourcing Inquiry
Tracking ID
tk_93bfa75bc8144b38879d824c1a5d7950
Location ID
6SQNS3XTMXx9wJ2GMzi0
Project ID
1793818487210392470

Standard contact fields (first/last name, email, phone, country, website, organization, timezone) are mapped automatically. Non-standard sourcing fields — inquiry reference, project name/type, service mode, destination, budget + currency, required-on-site date, decision maker, submission event ID, and per-item reference/category/quantity/UOM/ dimensions/material/target cost — must be registered as custom fields before activation, then passed through the tracking helper's customFields option using their returned IDs. Do not invent placeholder keys.

ONE PROJECT = ONE OPPORTUNITY. The tracking event records a submission; the CRM pipeline and opportunity-creation workflow (WF1) turn it into one opportunity per project. Enable account-level multiple-opportunity support and configure the Create Opportunity action's duplicate behavior before launch.

Sourcing pipeline

A dedicated "DITC Sourcing & Procurement" sales pipeline (preserve existing pipelines). ONE PROJECT = ONE OPPORTUNITY. A builder's 30-item package creates one opportunity with 30 child items; the same buyer's new project creates another opportunity under the same contact.

1. New Inquiry
→
2. Awaiting Client Information
→
3. Qualified / Scope Review
→
4. Supplier RFQs in Progress
→
5. Quotation Sent
→
6. Client Decision / Agreement Pending
→
7. On Hold

Use appropriate Open/Won/Lost CRM status and a loss/hold reason. A timeout or unanswered reminder alone must not automatically mean Lost. Mark Won only on approved commercial acceptance + payment conditions. Keep unconfirmed opportunity value blank/zero or use a deliberately approved estimate basis.

Configuration status

App backend (project drafts)

Projects, items, document metadata and submission state are stored in the Cloud database (sourcing_projects), RLS-scoped to the signed-in user.

Cloud-backed — durable per user

CRM intake / opportunity creation

Form-tracking integration connected. Tracking helper ready; no event fires until owner approval. WF1 recipe provided.

Wired — inactive (launch not approved)

Internal tasks & review deadlines

WF2 recipe provided.

Inactive — needs owner approval

Email sender

No messages sent in review. Five drafts provided.

Inactive — needs owner approval

Follow-up workflows (WF3–WF7)

Recipes provided; kept inactive until launch approval.

Inactive — needs owner approval

File privacy

Private sourcing-docs bucket with RLS policies scoping files to the owning user. Uploads require sign-in.

Cloud storage — private bucket

Authentication

Email sign-up/sign-in via Cloud auth. Sourcing inquiry & projects require sign-in. Academy entitlement preserved separately.

Cloud email/password — active

Setup recipe (manual steps)

Sourcing pipeline
Needs confirmation
  • Create a dedicated "DITC Sourcing & Procurement" sales pipeline (preserve existing pipelines).
  • Open stages: New Inquiry → Awaiting Client Information → Qualified / Scope Review → Supplier RFQs in Progress → Quotation Sent → Client Decision / Agreement Pending → On Hold.
  • Enable account-level multiple-opportunity support so one contact can hold several projects.
  • Configure the Create Opportunity action's duplicate behavior and opportunity-workflow multiple-execution settings for repeat clients.
Custom fields / objects
Needs confirmation
  • Create a Custom Object or fields for Sourcing Item (linked to Opportunity, not Contact): item reference, category, description, quantity, UOM, dimensions, material, target cost, currency, notes.
  • Create fields on Opportunity: Inquiry reference, Project ID, Service mode, Destination country/city, Delivery type, Budget + currency, Required-on-site date, Decision maker, Submission event ID, CRM opportunity ID.
  • Store the inquiry↔opportunity mapping server-side; do not rely on contact-name or earliest/latest opportunity matching.
Inquiry intake (WF1)
Not configured
  • Trigger: the connected "AI Studio Form Submitted" trigger filtered to this sourcing form, OR a supported server integration when the app backend is authoritative. Use ONE path only.
  • Validate reference + deduplicate via server-side uniqueness guard / event ledger.
  • Match/create the correct contact by verified normalized email; normalize phone only when supplied. Never merge by name/company.
  • Create ONE opportunity for a new project; update an existing project by its exact opportunity ID.
  • Assign pipeline/stage/source/owner, add structured summary + secure project link, create review task + internal notification.
  • Exclude drafts, out-of-scope tests and academy-only signups.
Internal review & deadlines (WF2)
Not configured
  • Create an internal review task due within one business day of acceptance (configurable DITC working calendar, Asia/Shanghai for China coordination).
  • Escalate overdue/unassigned work internally; flag urgent arrival/delivery dates without promising feasibility.
  • Client silence must not hide a DITC task; stopping external reminders must not stop internal obligations.
Missing information (WF3)
Not configured
  • Run only while Awaiting Client Information and specific required facts remain missing.
  • Reminders: after two business days, then around business day five. Stop on info arrival, client reply, coordinator takeover or stage change.
  • After the final reminder create a manual review/hold task; do not chase indefinitely or auto-lose.
Quotation follow-up (WF4)
Not configured
  • Start only after a human-approved quotation is sent/available and the opportunity is in the correct stage. Anchor timing to the sent date.
  • Reminders: two business days, then around business days five and ten. Identify project, quote reference/version, valid next action.
  • Suppress on reply, revision, decision, expiry, hold, staff takeover, opt-out or acceptance. Never resend expired pricing as valid.
Reply / takeover / suppression (WF5)
Not configured
  • Use Customer Replied, staff-reply/human-takeover and record-update events plus Stop on Response settings.
  • A reply to one workflow does not stop every other workflow; stop the relevant external sequence explicitly; retain internal tasks.
  • Match reply/conversation/subject to the exact project. If ambiguous across projects, pause routine chasing and assign a human triage task.
China visit preparation (WF6)
Not configured
  • Run only for the relevant confirmed visit and itinerary version.
  • Checklist ~7 days before arrival; confirmed appointment reminder 1 day before. Suppress outdated reminders on reschedule/cancellation.
  • Missing/tentative dates create internal clarification tasks, not invented bookings.
Acceptance & onboarding (WF7)
Not configured
  • On verified commercial acceptance + agreement/payment conditions: stop sales follow-ups, update the correct opportunity, create onboarding/procurement tasks, record approved spec/quote versions.
  • Do not treat opened email, clicked link or generated quote as acceptance/payment.
Channels, timing & guards
Needs confirmation
  • Email primary; enable SMS/WhatsApp only for selected, approved setup + consent + templates.
  • Use client-stated timezone for 09:00–17:00 Mon–Fri outbound windows; conservative fallback if unknown. Report any calendar implementation gap.
  • Limit routine automated chasing to at most one per contact per rolling 24h (configurable); consolidate or create a manual task for multi-project contacts.
  • Before each send recheck stage, missing data, quote version, recent activity, suppression, preference, sender availability and send history.
Email sender & templates
Not configured
  • Owner approves sender identity + the five message drafts (receipt, missing-info, quote follow-up, final check-in, visit reminder) before activation.
  • Map bracketed labels to actual supported fields; validate mappings; safe fallbacks; block sends when essential project/link data is absent.
File privacy & authentication
Needs confirmation
  • Private uploads require Cloud storage with server-enforced per-project authorization; never public buckets for drawings/quotes.
  • Reuse supported secure authentication; preserve the academy's separate entitlement. Do not authorize from URL, email match, CRM tag or localStorage.

Approval decisions for activation

  • • Owner approves launch, sender identity and the five message templates.
  • • Owner approves CRM intake path (one integration only) and opportunity duplicate/multiple-execution settings.
  • • Owner approves SMS/WhatsApp channels, consent and templates (email primary by default).
  • • Owner approves the configurable working calendar, business-hour windows and 24h contact chase limit.
  • • Enable Cloud for durable per-user projects, documents, quotations, authentication and protected file storage.