> ## Documentation Index
> Fetch the complete documentation index at: https://docs.assistable.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Create a follow-up task for a support request

> Capture an unresolved issue as a task on the connected GoHighLevel contact.

Use the platform **Create Task** tool to record an issue that needs human follow-up. This creates a GoHighLevel contact task. A ticket in a separate help desk requires that system's own integration.

## Before you start

Use an assistant with a working GoHighLevel connection and a conversation linked to the intended contact. Decide what information the team needs and how tasks are assigned and monitored.

## Add the task workflow

1. Open the assistant's **Tool Kit → Tools & APIs**.
2. Add **Create Task** (`create_task`).
3. In the assistant's instructions, require a short issue title, the customer's description, troubleshooting already attempted, and a confirmed callback method.
4. Tell the assistant to confirm the request with the customer before creating the task. Require a successful tool result before saying it has been recorded.
5. Specify the due date and assignee when your workflow needs them. The task supports a title, description, due date, assignee, and completion state. Without an explicit due date, the native handler defaults to one day later; this is not a promised response time.
6. Save and publish the assistant.

A suitable instruction is:

> When the issue needs human help, summarize it and confirm the best callback details. Create one follow-up task containing the issue and steps already tried. If the task cannot be confirmed, tell the customer it needs manual follow-up. Do not promise a response time we have not provided.

## Task fields

| Field | Accepted parameter names | Requirement or default |
| - | - | - |
| Title | `task_title`, `title` | Required, along with linked location/contact context. |
| Description | `task_description`, `description`, `body` | Optional task details. |
| Due date | `due_date`, `dueDate` | Optional; defaults to one day after creation when omitted. Supply an explicit date/time your GHL workflow accepts when the due time matters. |
| Assignee | `assigned_to`, `assignedTo` | Optional GHL user identifier; a person's display name is not an identifier. |
| Completed | `completed` | Boolean; defaults to `false`. Use `false` for work that still needs follow-up. |

The task is created on the resolved contact. Do not ask the assistant to manufacture a location, contact, or assignee ID. The handler does not automatically retry task creation; inspect the contact's task list if the first result is uncertain.

## Verify the result

Run a test support conversation. Open the correct GoHighLevel contact and inspect its task list. Check the title, description, due date, assignee, and incomplete status. Confirm that the team responsible for follow-up can find the task.

Do not equate a created task with a delivered notification. Configure and test any team notification separately.

## Troubleshooting

* **Missing contact or connection:** resolve the linked contact and reconnect the correct GoHighLevel account.
* **Task has no useful description:** make the collection and confirmation instructions explicit.
* **Uncertain timeout:** inspect the task list before submitting again. Repeating creation can create another task.
* **Need a help-desk ticket number:** connect a custom tool to your help desk and verify the returned ticket ID there.

[Platform tools](/v3/platform-tools) · [Save contact details](/v3/guides/workflows/save-contact-details) · [Custom API tools](/v3/guides/tools/custom-api)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.