> For the complete documentation index, see [llms.txt](https://help.pickyassist.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.pickyassist.com/changelog/2020/march-2020.md).

# March 2020

## March 28, 2020

### Timeout in Webhooks

1. Implemented timeout in webhooks , timeout is 60 seconds

## March 13, 2020

### Updates in Settings

1. Phone Automation Settings, WhatsApp , SMS & Calls are now grouped as "Phone Automation"
2. Now Device ID can be change from Settings -> Channels ->  Phone Automation -> Device [Read More](broken://pages/-M2JFlEQyJkoEEBIdRPA#changing-device)
3. New Project Creation flow is optimised&#x20;
4. Webhook for New Projects created on or after March 13, 2020 supports only JSON Method.

## March 5, 2020

### Following Features Made from Beta to Live

1. WhatsApp Official API Integration moved from beta to stable
2. Facebook API integration moved from beta to stable&#x20;


---

# 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://help.pickyassist.com/changelog/2020/march-2020.md?ask=<question>&goal=<endgoal>
```

`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.
