# Message Preview

### Message Preview

This is how your message will look like:

<figure><img src="https://file.go.gov.sg/message-preview.png" alt=""><figcaption><p>Message Preview</p></figcaption></figure>

#### **Header**

The `Header` corresponds to the email account that you have logged into Postman with.

You may check on the email account that you've used to log into Postman by clicking on the avatar at the bottom right of the page. Refer to the image for more information

{% hint style="info" %}
If you have more than 1 official email address belonging to different agencies, ensure that you have [logged in with the correct email address](/postman-v2-general-user-guide-mop/logging-into-postman-v2.md#singpass-login).
{% endhint %}

<figure><img src="/files/pcm4rGPNjxL7wanowRFP" alt=""><figcaption><p>Click on the avatar (bottom left) of page to check for the email address used to log into Postman</p></figcaption></figure>

#### Changing your message header

Header name changes are permitted in specific cases, and approved on a case-by-case basis. Some examples where header name changes are permitted.

**Platform products**&#x20;

Some products are used by multiple agencies, and recognised by the product name rather than agency name e.g. "Singpass", and not "Government Technology Agency". If you need to change the name in the header, please [contact us ](https://form.gov.sg/657025a2d2bd350012c82eb0)with your use case.

**An agency sending on behalf of another agency**

If you are helping another agency send messages, the main agency should add your agency's users as members/admins to the campaign so they are able to send messages from the main agency's created campaign. Please [contact us](https://form.gov.sg/657025a2d2bd350012c82eb0) if you need further clarification for your specific use case.

**Cases where header name changes are not permitted**

If your agency has a project that sends out surveys or information on welfare packages etc, these do not qualify for header name changes.


---

# Agent Instructions: 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:

```
GET https://postman-v2.guides.gov.sg/postman-v2-general-user-guide-mop/create-campaign/message-preview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.