[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"marketing:en:\u002Fsolutions\u002Fsupport:solution":3,"_apollo:default":82},{"contractVersion":4,"template":5,"slug":6,"eyebrow":7,"outcome":8,"capabilitiesTitle":9,"capabilities":10,"workflow":23,"proof":39,"closing":42,"faq":45,"cta":61,"id":64,"title":65,"body":66,"description":72,"extension":73,"meta":74,"navigation":75,"path":76,"seo":77,"stem":80,"__hash__":81},2,"solution","support","Support","The queue stops being a wall of unread messages and turns into a short list of cases that genuinely need you.","What makes a resolution faster",[11,14,17,20],{"title":12,"description":13},"A queue that knows what’s urgent","A third message from someone nobody answered goes to the top, whichever connected channel it arrived in.",{"title":15,"description":16},"Answers grounded in your knowledge","The agent replies from material you approved. Where a claim matters it carries the page it came from, so anyone can check it without coming to you.",{"title":18,"description":19},"You see the anger coming","The same question asked twice. Sentences getting shorter. A date you promised that has now gone past. All of it is visible while the thread can still be saved.",{"title":21,"description":22},"Edits and deletions stay on the record","A message that was rewritten or taken back is still readable, so nobody answers a sentence that isn’t there anymore.",[24,27,30,33,36],{"title":25,"description":26},"Understand the case","Today’s request and last month’s attempt at the same problem open side by side, with the policy that applies here.",{"title":28,"description":29},"Answer from what you approved","For questions with one right answer, the agent writes the reply out of your knowledge base and shows which part came from where.",{"title":31,"description":32},"Stop where judgment starts","A refund outside policy, an angry regular, anything with money or a promise attached. The agent prepares the reply and waits instead of sending it.",{"title":34,"description":35},"Hand it over cleanly","Whoever picks the thread up already knows what was tried, how the customer sounds by now, and what the next step is, so the customer never explains the same thing twice.",{"title":37,"description":38},"Confirm the outcome","Solved or not, what was promised, and what still remains, written down on the conversation.",{"title":40,"description":41},"What actually happened to the request","Dialog Man keeps what the issue really was, who took it, and how it ended. When a reply doesn’t reach the customer it shows up as a failure with the reason, not as a green checkmark.",{"title":43,"description":44},"Take the repetition out of the queue","Connect the channel people already write to. Give the agent your three most frequent questions and see how much of the queue still needs you.",{"eyebrow":46,"title":47,"items":48},"Questions","What support teams ask",[49,52,55,58],{"title":50,"description":51},"Will people notice an agent answered?","The tone follows your knowledge and your instructions, and nothing on the message labels it as automated. Where a human answer matters, the thread comes to you instead.",{"title":53,"description":54},"What if the agent answers badly?","Lower its autonomy or switch it off. New runs stop at once, and everything that already ran stays in the log with its reasons.",{"title":56,"description":57},"Can several people work the same queue?","Yes. A thread has one owner at a time, and everyone can see who that is. The note you leave at the end of your shift is the first thing the next person reads.",{"title":59,"description":60},"Does it work across channels?","Telegram, Instagram, and WhatsApp land in the same queue, and the history follows the person rather than the channel they happened to pick today.",{"label":62,"to":63},"Run support with Dialog Man","\u002Fauth\u002Femail?intent=business","marketing_en\u002Fsolutions\u002Fsupport.md","Resolve the issue before it becomes a relationship problem",{"type":67,"value":68,"toc":69},"minimark",[],{"title":70,"searchDepth":4,"depth":4,"links":71},"",[],"Everything this person has written to you before, the answers you approved, and the temperature of the thread arrive together. Routine questions close themselves, and the hard ones reach a person while there’s still time to fix it.","md",{"contractVersion":4,"template":5,"slug":6,"eyebrow":7,"outcome":8,"capabilitiesTitle":9,"capabilities":10,"workflow":23,"proof":39,"closing":42,"faq":45,"cta":61},true,"\u002Fsolutions\u002Fsupport",{"title":78,"description":79},"Dialog Man for customer support","Resolve requests across Telegram and Instagram with the full history, knowledge-grounded answers, early risk signals, and a clean handover to a person.","solutions\u002Fsupport","7SqGb-N9-SLw8lOuI8_2mer1IpRPcL0pE65k-UM9fmM",{}]