CRM Pre-Launch QA Checklist
Use this checklist before using GEVADE CRM with live customers, leads, campaigns, forms, workflows, booking links, or AI-assisted tools. A careful launch review helps reduce avoidable issues and gives support better information if something needs review.
Who this guide is for
- Account owners
- Admin users
- Marketing users
- Operations users
- Teams preparing to launch workflows, forms, campaigns, or booking flows
Pre-Launch Checklist Sections
1. Account access
- Account owner confirmed.
- Admin users reviewed.
- Billing access reviewed.
- Team permissions checked.
2. Business information
- Business name checked.
- Contact details checked.
- Time zone checked.
- Service areas checked.
- Operating hours checked.
- Support details checked.
3. Contacts and companies
- Import file reviewed.
- Duplicate contacts checked.
- Tags reviewed.
- Custom fields reviewed.
- Test contacts separated from live contacts.
4. Leads and pipelines
- Pipeline stages reviewed.
- Lead source tracking checked.
- Assigned users reviewed.
- Manual follow-up process documented.
5. Forms and funnels
- Form submits correctly.
- Contact is created or updated correctly.
- Required fields checked.
- Redirect or thank-you page works.
- Notifications are received.
- Mobile layout is reviewed.
6. Calendars and bookings
- Availability checked.
- Booking links tested.
- Appointment confirmation checked.
- Buffers reviewed.
- Reschedule and cancellation handling reviewed.
7. Communication tools
- SMS, email, WhatsApp, phone, or conversation setup reviewed where enabled.
- Message wording checked.
- Opt-out handling reviewed where relevant.
- Test messages sent.
8. Workflows
- Trigger tested.
- Actions reviewed.
- Wait steps checked.
- Stop conditions reviewed.
- Test contact used.
- Expected and actual results compared.
9. AI-assisted tools
- Business information reviewed.
- Response boundaries defined.
- Escalation rules tested.
- Sensitive topic rules reviewed.
- Incorrect answers corrected.
10. Reporting and support
- Dashboard filters checked.
- Key reports reviewed.
- Support request process understood.
- Screenshots and examples prepared where needed.
Recommended Links
When to Request Support
Submit a support request if any customer-facing process does not behave as expected during testing.
