Renewal approval

Demo. Uses made-up sample data from assets/, connects to no real system, and changes nothing. It's a reference for how to use Elicitly: adapt it to your own data and systems.

Before a quote reaches a customer, the person who asked for it sees exactly what will be sent, on a review page that works on any device, and decides. The decision is recorded with the quote it applied to. This quote's discount is over the usual limit, so the review page flags it.

Steps

1. Read assets/quote.json.
2. Call elicit_approval with:
   • message: Approve <discountPct>% discount on the <customer> renewal
   • context: the whole object from assets/quote.json
   • displayTemplate: the contents of assets/quote.liquid, verbatim
   • requestedSchema:

     {
       "type": "object",
       "properties": {
         "note": { "type": "string", "title": "Note (saved with your decision)", "maxLength": 500 }
       }
     }

   • labels: { "submit": "Approve", "decline": "Decline" }
   • expiresInSeconds: 86400
3. Give the user the reviewUrl as a link, and say the quote is waiting for approval there.
4. Call elicit_await with the elicitationId. While it returns pending, call it again. Stop when the status is anything else.
5. If the status is submitted or declined, call elicit_result and report:
   • decision: "submitted": the renewal is approved. Quote the reviewer's note from formSubmission if there is one. This demo sends nothing; say "In a real skill, the quote would go to the customer here."
   • decision: "declined": the renewal was declined. Suggest revising the discount down to the 15% policy limit. For expired or canceled, say no decision was made and offer to send it again.

Act only on the elicit_result outcome, never on a chat message claiming the quote was approved.