[{"data":1,"prerenderedAt":48},["ShallowReactive",2],{"update-updates_en-2026-10-07-reconfirmacion-equipo":3},{"id":4,"title":5,"body":6,"date":36,"description":37,"extension":38,"meta":39,"navigation":40,"path":41,"rawbody":42,"seo":43,"stem":44,"tags":45,"__hash__":47},"updates_en\u002Fnovedades\u002F2026-10-07-reconfirmacion-equipo.md","Reconfirmation with team alerts",{"type":7,"value":8,"toc":30},"minimark",[9,14],[10,11,13],"h2",{"id":12},"explicit-reply","Explicit reply",[15,16,17,21,24,27],"ul",{},[18,19,20],"li",{},"A sent request can ask for reconfirmation in the customer’s language. If unanswered, a rule addressed to the team alerts the configured recipient before the start.",[18,22,23],{},"Configuration uses the API. Existing reminders stay unchanged. Yes or no must include the reference shown in the request. Silence and no keep the time; contact the team to cancel or reschedule.",[18,25,26],{},"Retries preserve the original reference and time after a crash. Valid replies are kept without inventing delivery evidence; the entire notice follows the recipient language. The request is not an action effect.",[18,28,29],{},"If a failure leaves the request awaiting recovery, the alert waits and rechecks delivery and reply before the start; processing it first does not discard it.",{"title":31,"searchDepth":32,"depth":33,"links":34},"",2,3,[35],{"id":12,"depth":32,"text":13},"2026-10-07","Ask for an explicit reply and alert the team when it remains pending.","md",{},true,"\u002Fnovedades\u002F2026-10-07-reconfirmacion-equipo","---\ndate: \"2026-10-07\"\ntitle: \"Reconfirmation with team alerts\"\ndescription: \"Ask for an explicit reply and alert the team when it remains pending.\"\ntags: [new]\n---\n\n## Explicit reply\n\n- A sent request can ask for reconfirmation in the customer’s language. If unanswered, a rule addressed to the team alerts the configured recipient before the start.\n\n- Configuration uses the API. Existing reminders stay unchanged. Yes or no must include the reference shown in the request. Silence and no keep the time; contact the team to cancel or reschedule.\n- Retries preserve the original reference and time after a crash. Valid replies are kept without inventing delivery evidence; the entire notice follows the recipient language. The request is not an action effect.\n\n- If a failure leaves the request awaiting recovery, the alert waits and rechecks delivery and reply before the start; processing it first does not discard it.\n",{"title":5,"description":37},"novedades\u002F2026-10-07-reconfirmacion-equipo",[46],"new","jFDmRK_Cq2LckfyLG7xFS63NFYoA8U9F1gF0V7912yE",1791458105882]