# Client Communication

## Overview

Client communication is important for keeping in touch with your client and keeping them happy during the engagement. If a pentest is going well (for the client) then you might only reach out to them a couple of times.

When you have a critical finding like being able to get into their internal network through their VPN, get RCE or log into a web server, they need to know the **immediately.** Reach out via email or phone.

If we breach the internal network from the outside, there is a good chance that someone else has already done it. They need to know this so they can work on patching it immediately.

## Email Examples

<figure><img src="/files/a9qChp5YKZt87YXtFhNA" alt=""><figcaption><p>From course video</p></figcaption></figure>

The client needs to know what IP you will be attacking from so you're not mistaken from any real threats

You can have the email be sent automatically and even have the Nessus scans auto run minutes after. Automating some of the beginning processes are very helpful.


---

# 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://pnpt.adot8.com/external-pentest-playbook/before-starting/client-communication.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.