> For the complete documentation index, see [llms.txt](https://guide.smarttask.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.smarttask.io/crm-and-sales-management/sales-activities.md).
# Logging Sales Activities
Salespeople often juggle multiple prospects simultaneously, making it challenging to recall previous conversations and critical details that could make or break a deal. That’s where SmartTask steps in to help.
With SmartTask, you can effortlessly maintain a record of all customer interactions and quickly refer back to past discussions—ensuring you're always prepared for the next conversation.
**How to Maintain a Contact’s Activity Feed in SmartTask:**
1. Select the task associated with the client interaction.
2. In the task detail view, click the **More** button and choose **Attach Contact**.
3. In the modal, search for the contact's name.
4. *(Optional)* If the contact doesn’t exist, create a new one directly from the modal.
5. Once selected, the contact is linked to the task. The task will now appear in the contact’s activity feed for easy reference in the future.
Stay organized, close deals faster, and never miss a detail with SmartTask.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://guide.smarttask.io/crm-and-sales-management/sales-activities.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.