> For the complete documentation index, see [llms.txt](https://adly-news.gitbook.io/adly.news-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://adly-news.gitbook.io/adly.news-docs/02-newsletter-owners/07-messages.md). # Messages The messaging system allows you to communicate directly with businesses about their bookings. This guide explains how to use messages effectively. ## Accessing Messages ### Navigate to Messages 1. Click **Messages** in the sidebar 2. You'll see a list of all your conversations ### Understanding the Message List The messages page shows: | Information | Description | | ----------------- | ---------------------------------- | | **Business Name** | Who you're conversing with | | **Last Message** | Preview of the most recent message | | **Time** | When the last message was sent | | **Unread Count** | Number of unread messages | ### Unread Message Count At the top of your conversations, you'll see the total number of unread messages. The sidebar also shows a badge when you have unread messages. ## Viewing Conversations ### Open a Conversation 1. Click on any conversation in the list 2. The full conversation history opens 3. Messages are displayed chronologically ### Conversation Details Each conversation includes: * All messages between you and the business * Timestamps for each message * Image attachments (if any) * Connection to related bookings ## Sending Messages ### Compose a Message 1. Open the conversation 2. Type your message in the input field at the bottom 3. Press **Enter** or click **Send** ### Attaching Images If you need to share images: 1. Click the image/attachment icon 2. Select an image file 3. The image will be uploaded and sent ### Message Best Practices **Do:** * Be professional and courteous * Respond promptly to inquiries * Provide clear, helpful information * Confirm important details in writing **Avoid:** * Sharing personal contact information outside the platform * Conducting transactions outside the platform * Unprofessional language or behavior ## When to Use Messages ### Before a Booking Messages are typically initiated after a booking is confirmed. However, there may be pre-booking communication about: * Clarifying ad slot details * Discussing specific requirements * Answering questions about your newsletter ### During a Booking Common topics during active bookings: | Topic | Example | | --------------------- | -------------------------------------------------- | | **Creative feedback** | "Could you adjust the image size to 600x300?" | | **Copy questions** | "Is the copy length acceptable for your format?" | | **Scheduling** | "Just confirming the ad goes out on Monday" | | **Clarifications** | "Can you provide more context about your product?" | ### After Publication Post-publication communication: * Confirming the ad was published * Sharing any feedback * Discussing future opportunities * Thanking them for their business ## Conversation Organization ### Conversations by Booking Conversations are linked to the business you're working with. All messages with a particular business appear in the same conversation thread. ### Finding Specific Conversations If you have many conversations: 1. Scroll through the list 2. Conversations with unread messages appear with a badge 3. Recent conversations appear at the top ## Notifications You'll receive notifications when: * A new message arrives * The business responds to your message Configure notification preferences in [Settings](/adly.news-docs/02-newsletter-owners/10-settings.md). ## Message Etiquette ### Response Time Aim to respond to messages within: * **Urgent matters:** Same day * **General questions:** Within 24 hours * **Non-urgent topics:** Within 48 hours Quick responses build trust and lead to smoother bookings. ### Professional Communication Maintain professionalism: * Use proper grammar and spelling * Be clear and concise * Stay positive and solution-oriented * Address concerns constructively ### Handling Issues If problems arise: 1. Stay calm and professional 2. Understand the issue fully before responding 3. Propose solutions when possible 4. Escalate to platform support if needed ## Messaging and Bookings ### Accessing Booking Information While messaging, you may need to reference: * Booking details (see [Managing Bookings](/adly.news-docs/02-newsletter-owners/04-managing-bookings.md)) * Creative assets provided by the business * Scheduled dates and requirements Keep the booking page open in another tab for easy reference. ### Documenting Agreements Use messages to document any agreements: * Changes to creative * Rescheduling confirmations * Special requirements * Pricing discussions This creates a record that both parties can reference. ## Common Messaging Scenarios ### Requesting Creative Changes > "Hi \[Business Name], thank you for your booking! I noticed the image you provided is 800x600. Could you send a version at 600x300 to fit our newsletter format? Thank you!" ### Confirming Publication > "Hi \[Business Name], just wanted to let you know your ad went out in today's newsletter. Thanks for advertising with us!" ### Addressing Issues > "Hi \[Business Name], I'm checking on the CTA link you provided — it seems to be showing a 404 error. Could you verify and send a working link when you get a chance?" ### Following Up for Repeat Business > "Hi \[Business Name], it was great working with you on your recent campaign. If you're interested in running another ad with us, we have availability next month. Let me know if you'd like to discuss!" ## Privacy and Security ### Keep Communication on Platform * All business communication should happen through the platform * This protects both parties and creates records * Avoid sharing personal contact information ### Reporting Issues If you encounter inappropriate behavior: 1. Do not engage 2. Document the issue 3. Contact platform support 4. Platform can take action if needed ## Mobile Access Messages are accessible from mobile devices: * The interface adapts to smaller screens * Send and receive messages on the go * Get push notifications for new messages (if enabled) ## Common Questions ### Can I delete messages? Individual messages cannot be deleted. The conversation history is maintained for records. ### What if a business is unresponsive? Try messaging again after a day or two. If you need to reach them urgently about an active booking, contact platform support. ### Can I message businesses before they book? Messages are typically available for confirmed bookings. Pre-booking questions may need to go through the bidding or booking process. ### Are messages private? Messages are between you and the business. Platform support may access messages if there's a dispute or policy violation. ## Next Steps * View upcoming bookings in the [Calendar](/adly.news-docs/02-newsletter-owners/08-calendar.md) * Manage your [Bookings](/adly.news-docs/02-newsletter-owners/04-managing-bookings.md) * Set notification preferences in [Settings](/adly.news-docs/02-newsletter-owners/10-settings.md) --- # 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://adly-news.gitbook.io/adly.news-docs/02-newsletter-owners/07-messages.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.