Skip to content
KylothDesk
Kyloth DeskLiveSales, support and lasting relationships.

From first hello
to lasting customers.

From a new enquiry to a customer who comes back. Desk brings sales and support together, with a clear owner for the next step.

See how Desk works

Desk is live. New sign-ups are not open yet.

A woman wearing a headset listens beside a notebook and laptop.
Made for the human side of business.
The next promise01 / 03

Call Meera about the smaller option

PriyaFriday, 11:00 am
The context stays with the customer.
Generated editorial scene. Handover details are illustrative.
A little more context. A better next conversation.

For service businesses / Sales teams / Customer care

The complete journey we’re building

From the first hello to a customer who stays.

Kyloth Desk is being built for the work from start to finish. Begin with the parts your team needs, then add more as they become available.

  1. Meet

    Remember the person

    Keep customer details, enquiries and conversation history together, with permission for the people who need them.

  2. Follow up

    Give every enquiry an owner

    See who will call next, what the customer needs and how a possible sale is moving forward.

  3. Agree

    Make the next step clear

    Prepare a quote, keep track of changes and record the customer's decision before handing work to the next person.

  4. Help

    Carry the conversation through

    Turn a question into an assigned case. Resolve it, explain the answer and reopen it if the problem comes back.

  5. Keep in touch

    Learn from every conversation

    Review follow-ups and service quality. Use approved messages and AI drafts that a person checks before sending.

What you can explore

Follow the example customer story, inspect the sales and support workflow guides and use the handover template.

Still being completed

Channel connections, delivery reliability and AI-assisted communication still have provider and release checks. Public examples do not send messages to real customers.

Start with the problem you want to solve.

These are the subscription options we’re shaping. Choose a focused solution or bring the full product together. Prices and paid access are not open yet.

New sign-ups are not open yet. The full journey above describes the product direction, not a promise that every feature is ready today.

The details are the relationship.

They remember the promise.
Your team should, too.

A customer calls. Someone takes a note. Someone else picks up tomorrow. Desk gives that conversation a home, so the useful details can come along.

A small promise. A clear path.

From “I’ll get back to you”
to knowing who will.

Follow one customer enquiry through three simple steps. Choose a chapter to explore.

One customer. A connected story.
Kyloth DeskExample workspace
Customer enquiry

A smaller space. A clear request.

M
MeeraInterior consultation
The smaller option looks right. Could someone call me on Friday?
Priya Friday, 11:00 am

Meera needs the measurements before choosing.

Illustrative workflow · fictional people and details

One relationship. Room for every part.

Good business starts with
knowing the person.

Sales, customer care and the people doing the work. Connected by the same customer story.

01 / Sales & follow-ups

Keep the interest.
Know the next move.

“Send me the smaller option.” “Call after lunch.” Turn a useful conversation into a clear follow-up, with the quote and customer details close by.

  • Lead capture & import
  • Deals & flexible pipelines
  • Quotations & follow-ups
Explore Desk
A conversation taking shapeExample
EnquiryConversationQuote
M
Meera’s studioSpace planning · smaller option
“Can you check the size before sending the quote?”
Check measurementsPriya · Friday

The detail that matters is right beside the next step.

Two colleagues passing a folder across a meeting table.
Customer carePick up where the story left off.

Last note: check the replacement date.
Next update: today, 3:00 pm.

AArjun owns the next step
02 / Customer service

Help them move forward.
Without starting over.

When another teammate takes the call, the customer’s story should already be there. Keep cases, private notes and the next update together.

  • Shared inbox & tickets
  • Internal notes & saved replies
  • Service hours & response deadlines
See how the handover works
Customer timeline

A shared memory.
A more personal reply.

Notes, calls, deals and cases give the next teammate a place to start. Keep the details your business needs with custom fields.

Ownership & permissions

Clear responsibility.
A calmer day.

Give work an owner and due time. Find your next action in Today. Owners and admins decide who can access the workspace.

A useful habit. Yours to keep.

Leave a note.
Keep a promise.

You can start today, in the tools you already use. A good handover only needs four things.

  1. 01The need

    What matters to the customer?

  2. 02The promise

    What did we agree to do?

  3. 03The owner

    Who will take it from here?

  4. 04The time

    When should it happen?

Where Desk stands

Thoughtfully built.
Live, with its limits stated.

Explore what Desk does. Read the guide before asking about access.

Tested locally

01The workspace foundation

Customer records, leads, deals, follow-ups, quotes and cases have local test coverage. Desk works on its own, without a Commerce store.

Under review

02Real service connections

Messaging and AI need their own setup and real-account checks before public use. An example here does not mean a connection is live.

Next step

03Sign-up and pricing

Sign-up is coming soon and pricing is not confirmed. The Desk guide does not create an account or activate a paid plan.

What should we check before a paid plan?

Confirm the subscription, setup and support scope, hosting, storage and attachment limits, message charges and AI usage. Domain, image, video and content services need a separate scope if requested. These costs and allowances are not yet settled. Your team still records accurate context and reviews customer messages.

Read the current platform terms

The Desk guide

A thoughtful start.
One step at a time.

For approved access

Start small. Try a customer handover. Learn what each part can do before bringing it into your day.

Your Kyloth operator confirms access and setup. Sign-up is coming soon; reading this guide activates nothing.

01Workspace setupStart with one customer.A small, useful first run.
  1. 1

    Open your workspace

    Use the address and account supplied by your Kyloth operator. Create a workspace or choose one you belong to. You do not need a Commerce store.

  2. 2

    Try a simple follow-up

    Add a fictional customer, write a note and name the owner. Set a due time in India time. Check Today and the customer’s history to find it.

  3. 3

    Bring the right people in

    Owners and admins invite teammates and set up fields and pipelines. Members share workspace customer records. Assigning an owner does not make a record private.

  4. 4

    Review before importing

    Choose Customers → Import customers. Use Excel or CSV up to 1 MB and 200 rows. Map columns, fix errors and review the preview. Matching details never silently merge people.

02ChannelsConnect with care.One channel. The right checks.
  1. 1

    Begin with a manual case

    Link a customer, set the priority, name a teammate and record the request. Keep private team notes separate from replies to the customer.

  2. 2

    Check email before sending

    An owner or admin sets up email in Settings. It needs credentials, a verified sender domain and delivery checks. Review the recipient and message. Provider acceptance does not prove delivery.

  3. 3

    Know who is asking

    Incoming email needs a reviewed customer match. Hosted chat needs signed-in visitors and a configured service. Staff check identity before turning a conversation into a support case.

  4. 4

    Review each connection

    API keys have separate read and create permissions for contacts, leads and cases. Signed webhooks need activation and a verified receiver. WhatsApp still needs real-account acceptance. The Commerce connection is not publicly available.

03AI reviewA draft still needs your judgement.Read. Check. Then decide.
  1. 1

    Start with approved access

    Public AI activation is still pending. Model tests do not replace independent quality review. If the assistant is unavailable, keep working manually.

  2. 2

    Check the source

    Compare each claim with its cited notes. Clear up missing or conflicting information, then edit the draft. A citation alone does not make a claim true.

  3. 3

    Review before saving

    Confirm your review before saving an internal draft. Saving or copying sends nothing. Any later customer message needs its own recipient and content review.

  4. 4

    Keep a person in the loop

    Customer answers use approved knowledge and current access checks. Human handoff stays available. Imported website text cannot grant access to private records or authorise commitments.

04Data limitsKnow what stays. Know what moves.Clear boundaries for your records.
  1. 1

    Understand the export

    A manager can ask the Kyloth operator for a customer-directory export: up to 1,000 enrolled customers and 1 MiB. It does not include the full conversation, sales or financial history.

  2. 2

    Keep histories clear

    Customer identity links are reversible and do not merge histories. Deactivating a customer keeps the record. Neither action erases all data.

  3. 3

    Check an erasure request

    The reviewed policy covers selected saved assistant drafts only. It requires current manager approval and fresh hold and requester evidence. This guide does not enable real-workspace erasure.

  4. 4

    Know what remains

    Customer, financial and interaction records remain retained. Confirm the exact scope with your Kyloth operator before making any promise about deletion.

Looking for the storefront guide?Commerce user manual

Make asking for help feel like part of your brand.

Your customer should recognise your business when they need an answer. Discuss a branded help centre and customer portal, with clear paths to useful guides and their own cases.

Request a design quote How custom design works

From a question to a clear next step.

Ideas to shape your brief

  • Help-centre identity and layout
  • Guide categories and readable articles
  • Customer-portal presentation
  • Clear routes to supported contact options

A separate project. A clear quote.

Custom design is a higher-priced option than choosing a ready-made design. We quote the one-time design and development fee after discussing your business and scope. Your product subscription is separate.

Send an enquiry to discuss fit and availability. This does not book a project or take a payment. New customer sign-up remains closed.

Before you picture Desk
in your business.

Plain answers about the product, the plan and what is still being built.

A man reviewing an open notebook beside a closed laptop.
Illustrative scene
What is Kyloth Desk?

Kyloth Desk is a standalone CRM for sales and customer service. It connects customers, leads, follow-ups, deals and support. Desk is live, and sign-up is coming soon.

Can I use Desk without Kyloth Commerce?

Yes. Desk creates a workspace without a store, theme or checkout. Linking Commerce customers and orders remains planned and is not needed for the standalone workflows.

What has been verified in Desk?

Customer history, Excel/CSV import, lead capture, deal stages, follow-ups, quotations, team ownership, business fields and sales reporting have been tested locally. Support includes cases, internal notes, reviewed replies, service deadlines, published knowledge and an authenticated requester portal.

Can every teammate see every customer?

Current Desk members share customer records in their workspace. An owner filter organises work; it does not make a record private. Owners and admins manage team access and configuration. Requesters see only the public content they are authorised to access.

Which channels can we use?

Manual support, reviewed email intake and sending, and hosted authenticated chat have local acceptance coverage. Email still needs provider credentials, domain verification and live delivery checks; hosted chat needs its service configured. WhatsApp has local setup and messaging checks; real-account acceptance is still pending. These channels are not publicly available until those checks are complete.

Will AI send messages to my customers?

Saving a staff assistant draft sends nothing. A person checks sources, edits the words and reviews any later send separately. Some model tests have run, but independent quality approval and public activation are still pending. The requester-answer draft uses approved sources and preserves human handoff; it does not establish that an AI answer is safe to publish.

Can we bring our existing customer data?

Desk imports Excel or CSV files up to 1 MB and 200 rows, with mapping and error review before confirmation. A scoped API is implemented. Manager-authorised directory exports are limited to 1,000 customers and 1 MiB; they do not include the full conversation or financial history.

Will it fit the way our team works?

Desk supports configurable fields, pipelines, ownership and service hours. These controls describe your workflow; they do not certify an industry-specific regulatory requirement. Assignment remains a human decision, while supported reminders follow explicit rules.

Is Desk available, and what will it cost?

Desk is live, and sign-up is coming soon. Public pricing is not confirmed. The guide on this page is for approved access; it does not grant access or activate a paid plan.

Make the next conversation count.

Less “let me check”.
More “I remember”.