Audience: IT admin, admissions head, finance lead
Duration: ~1 hour
Prerequisites: IT admin · Communications playbook
Learning objectives
- Install connectors from CRM and ERP marketplaces
- Share credentials correctly across CRM + ERP
- Configure webhooks, telephony, and payment gateways
- Troubleshoot integration health
1. Where to open marketplace
| Product | Route |
|---|---|
| CRM | /school-panel/integrations |
| ERP | /erp/integrations |
Institution credentials are shared — install once, use in both products where supported.
2. Common connectors
| Category | Examples | Related guide |
|---|---|---|
| Messaging | WhatsApp, SMS, email | Communications playbook |
| Telephony | Twilio, MCube | Counselor § Telephony |
| Payments | Razorpay, Cashfree | Finance |
| AI / voice | AI voice agents | CRM AI |
Open each tile → Install → follow in-app setup wizard.
3. Telephony setup
After telephony app install:
Route: /school-panel/telephony-setup
Map numbers, IVR, and counselor click-to-call. Test with internal mobiles before campaigns.
4. Webhooks & API keys
| Route | Use |
|---|---|
/school-panel/webhooks |
Outbound events to your systems |
/school-panel/api-keys |
Custom API clients |
/erp/api-keys |
ERP-side automation |
Rotate keys periodically; store secrets in your password manager — not in email (IT admin).
5. Health & ops review
Integration failures surface in:
/school-panel/reviewor/erp/review(Operational review)- Connector detail page Test connection
Fix webhook URL reachability (HTTPS, no self-signed in production).
Practice exercise
- Install one demo connector (e.g. email or SMS sandbox).
- Run Test connection successfully.
- Map one WhatsApp or SMS template in template hub.
Troubleshooting
Install button disabled — Plan entitlement or role missing (Billing plans).
CRM works, ERP messaging fails — Same institution connector; re-save credentials on ERP communications settings.