PageSourceSearch

https://unbound.cx/_app/immutable/nodes/57.DdvtWmHT.js

js unbound.cx collected 2026-10-05 06:34:14 UTC 12,798 bytes, 14 lines download raw bytes

1import{c as We,l as Me,a as me}from"../chunks/BPQKp6QW.js";import{p as Oe,t as Re,f as pe,k as n,a as $e,b as he,c as Ie,u as ue,h as s,s as e,i as a,n as w,r as t,F as O,e as ve}from"../chunks/DpZX5E3g.js";import{w as Fe}from"../chunks/Dd6aOG2g.js";import{s as i}from"../chunks/CWDdQJS0.js";import{p as Le}from"../chunks/k0oaa6pU.js";import{h as c}from"../chunks/NmVdw5td.js";import{S as Ye}from"../chunks/DbPh46Rb.js";import{f as Ee}from"../chunks/BaWzH2I0.js";import{S as d}from"../chunks/ByyQVFMh.js";import{G as l}from"../chunks/zhos0mf6.js";import{D as Ue}from"../chunks/DqnaufOz.js";import{F as je}from"../chunks/DyTZcQ32.js";import{T as Ne}from"../chunks/z-rwaKIL.js";import{T as Qe}from"../chunks/DsyAubFB.js";o[O]="src/routes/[[lang=lang]]/solutions/saas/+page.svelte";var He=me(ve(`<li><time>8:10 AM</time><!> <!> <h3>A bot fixes a double charge.</h3> <p>This month’s bill came through twice, and the customer writes in. The bot finds both
2            charges on the account, credits one back inside your limit, and emails the customer to
3            say it’s done. When they ask for a receipt for their accountant, the bot sends that too.</p></li> <li><time>9:05 AM</time><!> <!> <h3>A person takes the refund request.</h3> <p>Then the customer asks for a refund on the whole year and to cancel. That&rsquo;s a call
4            you&rsquo;ve kept for people, so it goes to someone on the billing team with the thread,
5            the credit, the receipt, and the bot&rsquo;s notes already there.</p></li> <li><time>1:00 PM</time><!> <!> <h3>Sales sees the ticket.</h3> <p>The renewal is next month. The account executive sees this morning&rsquo;s double
6            charge, the credit, the receipt, and the request to cancel before the renewal call.</p></li> <li><time>4:00 PM</time><!> <!> <h3>Renewal signed on the record.</h3> <p>The rep sends the renewal for signature and collects payment in the same send.</p></li>`,1),o[O],[[76,8,[[77,10],[84,10],[85,10]]],[91,8,[[92,10],[99,10],[100,10]]],[106,8,[[107,10],[115,10],[116,10]]],[121,8,[[122,10],[130,10],[131,10]]]]),Ke=me(ve(`<!> <main class="pg-solutions-saas"><section class="hero"><div class="wrap hero-grid"><div class="hero-claim"><a class="crumb">&larr; All industries</a> <div class="eyebrow">Solutions · SaaS and software</div> <h1 class="h1-long">Run support and renewals from the same account.</h1> <p class="lede">Tickets, calls, chats, and the renewal land on one account. Support sees the deal, sales
7          sees the ticket, and a bot clears the routine questions before either one picks up.</p> <div class="ctas"><a class="btn" href="#try">Start free</a><a class="btn ghost" href="#talk">Talk to us</a></div> <!></div> <div class="hero-visual"><!></div></div></section> <section class="section alt" id="day"><div class="wrap"><div class="eyebrow">A day on Unbound</div> <h2>One account, one day, and nobody re-types a thing.</h2> <!> <p class="line day-note">A bot on your billing and support queues answers plan, seat, and how-to questions from your
8        billing data and help articles, credits within the limit you set, and sends the receipt. A
9        request to refund the year or cancel lands with a person, thread and all. <a class="dig">How bots work a support queue</a></p></div></section> <section class="section" id="queue"><div class="wrap split"><div><div class="eyebrow">Support queue</div> <h2>Tickets, calls, and chats in one queue.</h2> <p class="sub">Chat, email, SMS, voice, and video about one issue live on one task, routed by skill and
10          priority. A top account or a repeat contact moves up, and customers take a callback
11          instead of hold music.</p> <p class="links"><a class="dig">Omnichannel</a><a class="dig">Routing</a><a class="dig">Queues</a><a class="dig">Team chat</a></p></div> <!></div></section> <section class="section alt" id="account"><div class="wrap"><div class="eyebrow">One account record</div> <h2>Support sees the deal. Sales sees the ticket.</h2> <p class="sub">The renewal call, the open ticket, and the rollout meeting sit on the same company timeline,
12        so whoever picks up next already has the context.</p> <div class="grid4"><article class="card is-linked"><!> <div class="k">Companies</div> <h3>The account, rolled up.</h3> <p>People, deals, tickets, and conversations at the account, on the company.</p> <a class="dig">Companies</a></article> <article class="card is-linked"><!> <div class="k">Opportunities</div> <h3>Renewals on one board.</h3> <p>Renewals and expansions in a list or on a board. Call the buyer from the card.</p> <a class="dig">Opportunities</a></article> <article class="card is-linked"><!> <div class="k">Proposals</div> <h3>The renewal fills itself.</h3> <p>It pulls from the deal, the buyer, and the company, then goes out by email or text.</p> <a class="dig">Deals and proposals</a></article> <article class="card is-linked"><!> <div class="k">E-sign</div> <h3>Signature and payment in one send.</h3> <p>Binding e-signature built in. No e-sign license and no payment connector to maintain.</p> <a class="dig">E-sign</a></article></div></div></section> <section class="section" id="product-data"><div class="wrap split"><div><div class="eyebrow">Your product data</div> <h2>Your billing and product data, inside the conversation.</h2> <p class="sub">Connect billing and your own product in AI Workflows, and a bot or an agent answers a
13          plan, seat, or usage question in one turn instead of copying numbers between tabs. Keep
14          workspaces, licenses, and subscriptions as your own data on the account.</p> <p class="links"><a class="dig">Workflows and connections</a><a class="dig">Custom data</a></p></div> <!></div></section> <section class="section alt" id="faq"><div class="wrap"><div class="eyebrow">Questions</div> <h2>What support leaders ask before they switch.</h2> <!></div></section> <!></main>`,1),o[O],[[43,0,[[44,2,[[45,4,[[46,6,[[47,8],[48,8],[49,8],[50,8],[54,8,[[55,10],[55,51]]]]],[59,6]]]]],[71,2,[[72,4,[[73,6],[74,6],[134,6,[[137,82]]]]]]],[145,2,[[146,4,[[147,6,[[148,8],[149,8],[150,8],[155,8,[[156,10],[156,98],[159,11],[159,89]]]]]]]]],[175,2,[[176,4,[[177,6],[178,6],[179,6],[183,6,[[184,8,[[186,10],[187,10],[188,10],[189,10]]],[191,8,[[193,10],[194,10],[195,10],[196,10]]],[198,8,[[200,10],[201,10],[202,10],[203,10]]],[205,8,[[207,10],[208,10],[209,10],[212,10]]]]]]]]],[218,2,[[219,4,[[220,6,[[221,8],[222,8],[223,8],[228,8,[[229,10],[231,11]]]]]]]]],[244,2,[[245,4,[[246,6],[247,6]]]]]]]]);function o(ge,fe){We(new.target),Oe(fe,!0,o);const r=Re(ue(()=>Le.params.lang),"lang"),R=[{q:"Can a bot work our support queue next to our agents?",a:"Yes. It sits on the support queue like any agent, with its own skills and priority, and answers chat, email, SMS, and voice from the playbooks and knowledge base your team already uses."},{q:"What happens when the bot can’t answer?",a:"It hands the task over with the whole thread attached: what the customer asked, what the bot checked, and what’s still open. The customer picks up where they left off."},{q:"Can Unbound read our own billing and product data?",a:"Yes. Connect billing and your product in AI Workflows. Bots and agents use them on live tasks to pull the plan, confirm seats, or check usage."}
14,{q:"Does sales work on the same platform as support?",a:"Yes. Companies, opportunities, proposals, e-signature, and payment run on the same record support works. Support sees the renewal, and sales sees the open ticket."}];var be={...Me()},$=Ke(),I=pe($);{let p=ue(()=>[Ee(R)]);n(()=>Ye(I,{title:"Unbound: SaaS and Software",description:"Unbound lets SaaS and software companies run support tickets, calls, chats, and the renewal from one account record, with bots on the support queue too.",path:"/solutions/saas",get jsonLd(){return s(p)}}),"component",o,36,0,{componentTag:"Seo"})}var F=e(I,2),k=a(F),L=a(k),y=a(L),Y=a(y),we=e(Y,10);n(()=>Qe(we,{}),"component",o,57,8,{componentTag:"TrustLine"}),t(y);var E=e(y,2),ke=a(E);n(()=>d(ke,{img:"/shots/CCTaskTimeline-double-charge.webp",crop:"285,262,730,460",cropSm:"285,262,560,400",alt:"One billing task: the refund and cancellation request routed to a person, the receipt and credit the bot handled earlier, and its confirmation email",caption:"The refund request, handed to a person. Below it, the receipt and the credit the bot already took care of."}),"component",o,60,8,{componentTag:"Shot"}),t(E),t(L),t(k);var _=e(k,2),U=a(_),j=e(a(U),4);n(()=>Ue(j,{n:4,children:Fe(o,(p,ce)=>{var v=He(),h=pe(v),g=e(a(h));n(()=>l(g,{id:"bot",label:"Bot"}),"component",o,77,30,{componentTag:"Glyph"});var D=e(g,2);n(()=>d(D,{img:"/shots/CCDashboardCurrent-billing.webp",crop:"275,325,460,220",alt:"Task list with the charged-twice email completed by the Billing Bot and the refund and cancellation request with a person",caption:"The billing bot finished the double charge. The refund request is with a person."}),"component",o,78,10,{componentTag:"Shot"}),w(4),t(h);var u=e(h,2),f=e(a(u));n(()=>l(f,{id:"person",label:"Person"}),"component",o,92,30,{componentTag:"Glyph"});var W=e(f,2);n(()=>d(W,{img:"/shots/CCTaskTimeline-double-charge.webp",crop:"382,298,460,200",alt:"The billing task with the refund and cancellation email, marked as needing a person and routed to billing",caption:"The refund request, marked for a person and routed to billing."}),"component",o,93,10,{componentTag:"Shot"}),w(4),t(u);var m=e(u,2),b=e(a(m));n(()=>l(b,{id:"person",label:"Person"}),"component",o,107,30,{componentTag:"Glyph"});var M=e(b,2);n(()=>d(M,{img:"/shots/PeopleDetailActivity.webp",crop:"95,240,440,330",pins:"106,262|106,541",alt:"Account activity with a call and an open ticket",caption:"Today’s activity and an open ticket, on the same account feed."}),"component",o,108,10,{componentTag:"Shot"}),w(4),t(m);var le=e(m,2),de=e(a(le));n(()=>l(de,{id:"person",label:"Person"}),"component",o,122,30,{componentTag:"Glyph"});var De=e(de,2);n(()=>d(De,{img:"/shots/PeopleDetailActivity.webp",crop:"1050,415,380,285",pins:"1079,437|1094,650",alt:"Activity feed with an agreement sent and signed",caption:"The renewal goes out from the record and comes back signed on the same feed."}),"component",o,123,10,{componentTag:"Shot"}),w(4),t(le),he(p,v)}),$$slots:{default:!0}}),"component",o,75,6,{componentTag:"DayRibbon"});var N=e(j,2),ye=e(a(N));t(N),t(U),t(_);var T=e(_,2),Q=a(T),q=a(Q),H=e(a(q),6),K=a(H),z=e(K),J=e(z),_e=e(J);t(H),t(q);var Te=e(q,2);n(()=>d(Te,{img:"/shots/ContactCenter.webp",crop:"875,212,540,218",pins:"880,268|880,313|880,358",alt:"Task list with a callback, an email ticket, and a chat",caption:"A callback, an email ticket, and a chat, all in one list."}),"component",o,165,6,{componentTag:"Shot"}),t(Q),t(T);var S=e(T,2),V=a(S),X=e(a(V),6),C=a(X),Z=a(C);n(()=>l(Z,{id:"building"}),"component",o,185,10,{componentTag:"Glyph"});var qe=e(Z,8);t(C);var A=e(C,2),ee=a(A);n(()=>l(ee,{id:"record-card"}),"component",o,192,10,{componentTag:"Glyph"});var Se=e(ee,8);t(A);var x=e(A,2),ae=a(x);n(()=>l(ae,{id:"form"}),"component",o,199,10,{componentTag:"Glyph"});var Ce=e(ae,8);t(x);var te=e(x,2),oe=a(te);n(()=>l(oe,{id:"signature"}),"component",o,206,10,{componentTag:"Glyph"});var Ae=e(oe,8);t(te),t(X),t(V),t(S);var P=e(S,2),ne=a(P),G=a(ne),se=e(a(G),6),re=a(se),xe=e(re);t(se),t(G);var Pe=e(G,2);n(()=>d(Pe,{img:"/shots/WorkflowCanvas.webp",crop:"540,520,440,330",pins:"554,730|724,826",alt:"Workflow with a lookup step and a summary step",caption:"A lookup step reads your system mid-conversation, and the summary is saved to the account."}),"component",o,234,6,{componentTag:"Shot"}),t(ne),t(P);var B=e(P,2),ie=a(B),Ge=e(a(ie),4);n(()=>je(Ge,{get items(){return R},open:0}),"component",o,248,6,{componentTag:"Faq"}),t(ie),t(B);var Be=e(B,2);return n(()=>Ne(Be,{title:"See your support queue with a bot working it.",sub:"Open a free 30-day account with sample data, put a bot on the support queue, and watch a ticket close on the account sales is renewing."}),"component",o,252,2,{componentTag:"TryBlock"}),t(F),$e((p,ce,v,h,g,D,u,f,W,m,b,M)=>{i(Y,"href",p),i(ye,"href",ce),i(K,"href",v),i(z,"href",h),i(J,"href",g),i(_e,"href",D),i(qe,"href",u),i(Se,"href",f),i(Ce,"href",W),i(Ae,"href",m),i(re,"href",b),i(xe,"href",M)},[()=>c("/solutions",s(r)),()=>c("/platform/contact-center/bots",s(r)),()=>c("/platform/contact-center/omnichannel",s(r)),()=>c("/platform/contact-center/taskrouter",s(r)),()=>c("/platform/contact-center/queues",s(r)),()=>c("/platform/team/chat",s(r)),()=>c("/platform/crm/companies",s(r)),()=>c("/platform/crm/opportunities",s(r)),()=>c("/platform/crm/deals-proposals",s(r)),()=>c("/platform/crm/e-sign",s(r)),()=>c("/platform/infra/workflows-mcp",s(r)),()=>c("/platform/crm/objects",s(r))]),he(ge,$),Ie(be)}export{o as component};

Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.