1. Application status Q&A and scholarship guidance
Applicants flood the admissions office asking where their application stands and whether they qualify for a scholarship, and staff look each one up by hand and repeat the same eligibility rules dozens of times a day.
Trigger: WhatsApp / Webhook (applicant enquiry)
How the workflow runs
- Trigger
Applicant asks. A WhatsApp or Webhook trigger starts on any status or scholarship question, in the applicant's language.
- Agent
Identify the applicant. An Agent node verifies identity and the application reference before anything is looked up.
- Tool (MCP)
Fetch live application status. A Tool (MCP) node reads the current stage from your SIS/admissions system. There's no first-party connector — the status is fetched via MCP.
- Knowledge
Explain scholarship criteria. A Knowledge node answers financial-aid and scholarship questions strictly from the official criteria documents — grounded, with citations.
- Approval
Eligibility rulings go to an officer. An Approval node routes any actual eligibility or award decision to a financial-aid officer — the agent explains the rules, a human decides who qualifies.
- Output
Reply + record. An Output node sends the status and grounded guidance on WhatsApp and logs the interaction.
Channels & connectors
- Webhook
- Sarvam (22+ Indian languages)
- Knowledge base
- Approval / HITL
- Tool (MCP → SIS/admissions)
Outcome
Applicants get their real status and accurate scholarship guidance instantly, while any eligibility or award decision stays with a human officer.
Why it helps
Removes the manual per-applicant lookup and the hundredth repeat of the same criteria, while keeping every money/eligibility call with a person — the agent informs, it never rules.
Build spec
1 agent — 1 applicant-facing agent; the status lookup, the eligibility Approval and the reply/log are workflow nodes.
System prompt (paste-ready)
You are an admissions assistant for {{institution_name}}. Verify the applicant's identity and application reference before looking anything up. Report the application status the system returns, and answer scholarship and financial-aid questions STRICTLY from the official criteria documents in Knowledge, with citations. You EXPLAIN the criteria — you do NOT decide eligibility, confirm an award, or tell an applicant they qualify; any actual eligibility or award decision is a financial-aid officer's at the approval step. Reply in the applicant's language and never reveal another applicant's data.MCP connectors
- SIS / admissions system — via a Tool (MCP) node (no first-party connector)
- WhatsApp — via the messaging channel
- Sarvam — 22+ Indian languages
Built-in tools
- knowledge_search (scholarship + financial-aid criteria)
Guardrails
- Never rules on eligibility or confirms an award — it explains the criteria; the financial-aid officer decides who qualifies at the Approval node
- Identity + application reference are verified before any status lookup; an applicant only ever sees their own data
- Scholarship guidance is grounded in the official criteria with a citation, never an assumed or invented figure
Output & delivery
The agent verifies identity → a Tool node reads the live application stage from the SIS via MCP → a Knowledge node grounds scholarship guidance → any eligibility/award call goes to the financial-aid officer at the Approval node → an Output node sends the status and guidance on WhatsApp and logs the interaction.
