Batch 7.2: Support Request → Zoho Cases #76

New Issue

Closed

opened 2026-05-17 18:54:10 -05:00 by null · 0 comments

null commented

2026-05-17 18:54:10 -05:00

Owner

Batch 7.2 — Forward Support Requests to Zoho Cases

Phase: 7 — Zoho CRM Integration
Agent: Neo (backend)
Priority: P2 Medium — enhancement, not blocking

Problem

Support form submissions currently only write to SQLite. They should also create Cases (tickets) in Zoho CRM for ticket tracking, so support staff have visibility.

Tasks

Add ZOHO_CASES_ENABLED env var (separate from lead forwarding)
Create forwardSupportToZoho() function
Map form fields to Zoho Case schema:
- Subject (mandatory) — from support issue description
- Case_Origin (picklist) — "Website"
- Email — from form
- Phone — from form
- Priority — from form priority selection (if present)
- Description — full message + service interest
Reuse getZohoAccessToken() for auth
Fire-and-forget with .catch() (non-blocking)
Add to Dockerfile and .env.example
Test with ZOHO_CASES_ENABLED=false first

Files to modify

server/index.js — New forwardSupportToZoho() function, call from support route
Dockerfile — Add ZOHO_CASES_ENABLED
.env.example — Add ZOHO_CASES_ENABLED

Acceptance criteria

Support submissions write to SQLite first (always)
When ZOHO_CASES_ENABLED=true, also forwards to Zoho Cases
When ZOHO_CASES_ENABLED=false, no Zoho calls for support
Zoho Case payload matches required schema
No regressions in support form submission

## Batch 7.2 — Forward Support Requests to Zoho Cases **Phase:** 7 — Zoho CRM Integration **Agent:** Neo (backend) **Priority:** P2 Medium — enhancement, not blocking ### Problem Support form submissions currently only write to SQLite. They should also create Cases (tickets) in Zoho CRM for ticket tracking, so support staff have visibility. ### Tasks - Add `ZOHO_CASES_ENABLED` env var (separate from lead forwarding) - Create `forwardSupportToZoho()` function - Map form fields to Zoho Case schema: - `Subject` (mandatory) — from support issue description - `Case_Origin` (picklist) — "Website" - `Email` — from form - `Phone` — from form - `Priority` — from form priority selection (if present) - `Description` — full message + service interest - Reuse `getZohoAccessToken()` for auth - Fire-and-forget with `.catch()` (non-blocking) - Add to Dockerfile and `.env.example` - Test with `ZOHO_CASES_ENABLED=false` first ### Files to modify - `server/index.js` — New `forwardSupportToZoho()` function, call from support route - `Dockerfile` — Add `ZOHO_CASES_ENABLED` - `.env.example` — Add `ZOHO_CASES_ENABLED` ### Acceptance criteria - Support submissions write to SQLite first (always) - When `ZOHO_CASES_ENABLED=true`, also forwards to Zoho Cases - When `ZOHO_CASES_ENABLED=false`, no Zoho calls for support - Zoho Case payload matches required schema - No regressions in support form submission