Response Status
Represents workflow state.
Problem: You are not sure what the three status values mean technically — or why you cannot create a response in a status other than need_reply.
Solution: Response status is a lifecycle enforcer — every response starts at need_reply because the person has not yet been contacted, and progress only when real actions happen.
Type
type ResponseStatus = 'reply' | 'waiting' | 'done';Flow
reply → waiting → done
↑ |
└───────────────┘ (can move back if needed)Definitions
| Status | Meaning | When to Use |
|---|---|---|
| reply | Action required from you | Automatic on creation — all new responses start here |
| waiting | You replied, waiting on them | After you send a message, demo link, or meeting invite |
| done | Conversation finished | After demo, showing, or resolution — no further action needed |
Why You Cannot Create in Waiting or Done
A submission exists because someone showed interest and has not been contacted yet. The lifecycle starts at need_reply because that is the truth. Allowing creation in Waiting or Done would make your Inbox inaccurate from the start.
Result: You now understand each status and the reasoning behind the lifecycle enforcement — your Inbox always reflects what has actually happened.
Common Questions
What is the difference between waiting and completed?
Waiting means the conversation is active — you replied and expect a response back. Done means it is finished — no further action. Use Waiting while a deal is in progress. Use Done when it resolves.
Can a response move backwards from Done to Reply?
Yes. If a resolved conversation becomes active again (e.g. a past lead re-engages), you can reopen it and move it back to Reply.
Next
Metadata →