import{s as v,e as h,a as y,c as m,b as g,g as k,B as w,f as r,h as d,i as p,j as f,t as b,d as _}from"../chunks/scheduler.oLb3t87Q.js";import{S as T,i as $,c as S,b as x,m as B,t as C,a as H,d as A}from"../chunks/index.DGezeK-W.js";import{S as E}from"../chunks/SectionHeader.NOssM3Bd.js";function I(l){let e;return{c(){e=b("General Settings")},l(t){e=_(t,"General Settings")},m(t,n){p(t,e,n)},d(t){t&&r(e)}}}function K(l){let e,t,n,i,c='<p class="svelte-1f5kvet">The settings screen is where you can make changes to your company name, billing email, and other settings</p> <h2 class="svelte-1f5kvet">Company Name</h2> <p class="svelte-1f5kvet">The company name is what&#39;s shown everyone in the system, include outgoing emails.</p> <h2 class="svelte-1f5kvet">Billing Email</h2><p class="svelte-1f5kvet">This is the email you provided when signing up and at first is also your admin user email. But you can change it at any time. This email will get billing reminders 7 days before your next payment is due to be charged.</p> <h2 class="svelte-1f5kvet">Allow users to submit tickets for someone else</h2> <p class="svelte-1f5kvet">This setting determines if users are allowed to submit tickets on behalf of other users. This will allow them to search for anyone in your system and assign the ticket to them instead.</p> <h2 class="svelte-1f5kvet">Show KB article suggestions when users create new tickets</h2> <p class="svelte-1f5kvet">If enabled, <a href="/documentation/articles" class="svelte-1f5kvet">KB articles</a> will be suggested when users create new tickets. Suggestions will be based on keywords in their brief description compared to words in your KB articles</p> <h2 class="svelte-1f5kvet">Branding</h2> <p class="svelte-1f5kvet">This section is where you can use your own logo and primary color.</p> <h2 class="svelte-1f5kvet">Helpful Links</h2> <p class="svelte-1f5kvet">The ticket screen that all uses see has a list of helpful links above or below it. This is where you can manage that list.</p> <h2 class="svelte-1f5kvet">Statuses</h2> <p class="svelte-1f5kvet">You can create custom statuses in addition to the system-required statuses. The system statuses can not be changed as they are used for ticket automation.</p> <p class="svelte-1f5kvet">System Statuses</p> <ul class="normalUl"><li>Closed - Used to determine if a ticket is complete. This status is set automatically if <a href="/documentation/departments" class="svelte-1f5kvet">department</a> auto-close is enabled and the user has not responded in the set amount of days</li> <li>End User Responded - This status is set automatically every time the ticket submitter responds to a ticket, either throught the ticket system, or an email reply.</li> <li>New - This is the initial status of all newly created tickets</li> <li>Waiting On Customer - This status is set automatically when an owner of a ticket responds</li> <li>Waiting Overdue - This status is set automatically if <a href="/documentation/departments" class="svelte-1f5kvet">department</a> auto-reminder is enabled and the user has not responded in the set amount of days</li></ul> <p class="svelte-1f5kvet">Custom Statuses</p> <p class="svelte-1f5kvet">You can use the Add button on top of the status list to create your own statuses. At any point you can also edit, or remove your custom statuses.</p>',o;return t=new E({props:{class:"mb-3",$$slots:{default:[I]},$$scope:{ctx:l}}}),{c(){e=h("div"),S(t.$$.fragment),n=y(),i=h("div"),i.innerHTML=c,this.h()},l(s){e=m(s,"DIV",{class:!0});var a=g(e);x(t.$$.fragment,a),n=k(a),i=m(a,"DIV",{id:!0,"data-svelte-h":!0}),w(i)!=="svelte-166xz7z"&&(i.innerHTML=c),a.forEach(r),this.h()},h(){d(i,"id","content"),d(e,"class","")},m(s,a){p(s,e,a),B(t,e,null),f(e,n),f(e,i),o=!0},p(s,[a]){const u={};a&1&&(u.$$scope={dirty:a,ctx:s}),t.$set(u)},i(s){o||(C(t.$$.fragment,s),o=!0)},o(s){H(t.$$.fragment,s),o=!1},d(s){s&&r(e),A(t)}}}class z extends T{constructor(e){super(),$(this,e,null,K,v,{})}}export{z as component};