We are here to support you.
This article explains how Approvals work for customers in KDesk, including when contacts can see approval activity, how they respond, how email approval links behave, and how appeals work after a denial. What Approvals Do Approvals let a workspace pause a ticket or form-driven process until the right person or…
This article explains how Approvals work for customers in KDesk, including when contacts can see approval activity, how they respond, how email approval links behave, and how appeals work after a denial.
Approvals let a workspace pause a ticket or form-driven process until the right person or group reviews it. A customer-facing approval can be routed to a specific contact, to contacts already attached to the ticket, or to a larger approval path that includes both internal members and customer contacts.
Customers can encounter approvals in two main places:
If neither of those settings is enabled for contacts, the approval can still run internally for staff without exposing the approval activity to the customer.
When approval visibility is enabled for contacts, the ticket can show the approval title, current status, step names, assigned approvers, comments tied to approval decisions, and appeal details when an appeal is part of the workflow.
This lets a customer understand whether approval is still pending, who needs to respond, whether the request was approved or denied, and whether an appeal is waiting for review.
A customer can only submit an approval response when they are part of the current active step. If the approval is pending and the signed-in contact is one of the approvers on that step, the customer can approve or deny it.
If the contact is not assigned to the current step, the approval can still be visible on the ticket, but the response actions stay unavailable.
Email approval links open a dedicated response page that shows the approval title, description, current status, step details, and the person expected to respond. Depending on the team configuration, the customer may be required to sign in before they can submit the response.
If sign-in is required and the customer is not authenticated yet, KDesk sends them through the contact sign-in flow and then returns them to the approval response page. If the token has already been used, expired, or is no longer valid for the current step, the page shows that the link is no longer active.
Appeals are optional. A workspace must enable approval appeals, and the individual approval template must also allow appeals before customers can use that path.
When an approval is denied and appeals are available, a customer can request an appeal from the ticket approval view. KDesk requires an appeal reason, and that reason becomes part of the appeal request shown to the reviewers.
Once an appeal is active, only the assigned appeal reviewers can approve or deny the appeal. Regular ticket viewers can still see the appeal status when the workspace allows approval visibility on tickets.
If you are documenting approvals for your own customers, the clearest explanation is: KDesk can ask a customer contact to approve or deny a request directly from the portal or from an email link. The customer only sees approvals that their service team has chosen to expose, and they can only respond when they are the assigned approver for the current step.
Tickets Tickets are the main way KDesk tracks work. ...
This article explains the current KDesk Team Creation f...
This article explains how billing currently works in KD...