An answer you can trace. A send button you control.
Bring your existing information into one review screen, then decide what belongs in each customer reply.
Ask about the pilotPaste, don't rebuild.
Add the FAQ and product descriptions you already use. Shipping and returns text can go in too. EchoDesk is designed around the written answers you have, not a new knowledge-base project.
For the planned email-first pilot, connecting an inbox lets EchoDesk read new customer emails to prepare drafts. It does not send without your click.
One inbox, three clear states.
These illustrative screens show how a question moves from your inbox to your decision.
See what needs your attention.
New customer emails are organized by whether a draft is ready, needs your input, or cannot be answered from the material you provided.
Customer inbox
Read the reply beside its source.
Review a suggested draft, inspect where each sentence came from and adjust the wording before choosing to send. Example text here is illustrative, not a real business policy.
Suggested reply
Our shipping information is on the shipping page. Shipping FAQ
The owner reviews and sends. EchoDesk does not auto-send.
No source? No made-up answer.
When your material does not cover a question, the proposed flow flags it and blocks sending an unsupported draft. Write the answer yourself, then add it to your material if it comes up again.
Needs your answer
“Do you offer custom sizes?”
No draft is ready to send for this question.
Questions before you begin.
No. The planned workflow leaves sending to you after you review the draft and its sources.
The planned review flow marks it as a gap instead of making up an answer. You can answer personally and add that information for future questions.
Customer email is the proposed first channel. Other channels are not part of the described first workflow.
What questions keep coming back?
Those repeat questions are a useful place to start the conversation.