Answer Peerspace inquiries with your real availability and rules

1. Peerspace alerts you to a new inquiry by email, by text once your phone number is verified under the Profile tab, or by push in the Peerspace app; a reply to the notification email is routed to the guest.
2. Open the thread in the Peerspace Inbox and note what the guest is really asking: date, hours, headcount, activity, parking, load-in, noise.
3. Switch to the Calendar tab for that space to see whether the date is free; only accepted bookings mark time unavailable, while other inquiries and requests show there only for you.
4. Click the + icon under the thread, pick a message template, then edit in the guest's name and the specific answer before sending.
5. Every inquiry repeats this. Templates answer the stock question but not "is the 24th free for 40 people", and an inquiry read at midnight waits until morning.

Answer new Peerspace inquiries: check the date on the calendar, give our rate, parking and load-in details, and ask me about anything you do not know.

1. 01

   Find the threads waiting on you

   list_conversations with unanswered_only returns threads where the guest wrote last. New inquiries come first; a guest question on an already confirmed booking is listed apart, because it needs a different kind of answer.

2. 02

   Match the inquiry to the right listing

   get_conversation gives the whole thread, so earlier answers are not repeated. One space often has a shoot listing and an events listing at different base rates, and the agent uses list_listings to quote the rate of the listing the guest wrote about.

3. 03

   Check the date before saying yes

   get_calendar for the asked day decides the wording. Free means the reply says so. A confirmed booking means the reply offers the two nearest open days. A pending request from someone else means the reply says the slot is requested, without promising it.

4. 04

   Use your facts, never made-up ones

   Parking, load-in, noise and capacity answers come from what you gave the agent. A question it has no answer for (can we hang lights from the ceiling) is sent to you instead of guessed. Phone numbers, emails and outside payment links stay out of the reply.

5. 05

   Send, then point to the next step

   send_message goes out after your OK. When the guest has a date, hours and headcount settled, the agent says an invite-to-book is the next move rather than waiting for the guest to request.

5 unanswered inquiries.
Replied after your OK: Dana (Oct 24, 20 people, offsite): date free, $150/hour on the events listing, free parking for 6 cars.
Replied: Sam (Nov 2, music video): Nov 2 is booked, offered Nov 1 and Nov 8.
Replied: Alex (parking only): street parking and the loading zone on 3rd St.
Waiting on you: Robin asks if a 12 ft cyclorama is available; no answer on file.
Waiting on you: Chris wants to pay by bank transfer; Peerspace requires payment on the platform.

• Peerspace response time is the average number of hours to answer new inquiries and requests; follow-up messages do not count, and inquiries received in off hours or late evening do not hurt it.
• Peerspace says guests are 3x more likely to book when a host responds within 2 hours, and its top hosts usually reply within 1 hour.
• Peerspace may block or flag a message before delivery when it contains contact information or wording that suggests a deal off the platform.
• Peerspace hosts may agree to a site visit when a guest asks, but repeated visits that never turn into Peerspace bookings can lead to liquidated damages or suspension.

send_message asks for your OK by default. To run it daily without you, switch confirmation off for that tool in your dashboard.

Sources: Peerspace help: How do I maintain a healthy response time and response rate? · Peerspace help: Message Templates Feature · Peerspace help: Why keeping your bookings on Peerspace pays off · Peerspace help: Can I schedule a site visit with a guest before they book?

curl https://cotlet.dev/api/v1/peerspace/send_message \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"conversation_id":"c_58210437","body":"Hi Dana, Oct 24 is open for 20 people. Parking for 6 cars is free on site, and load-in is through the back door on 3rd St. Want me to send you an offer for the hours you need?"}'

{
  "message_id": "m_6204188",
  "conversation_id": "c_58210437",
  "status": "sent",
  "sent_at": "2026-10-11T09:05:00-07:00"
}

MCP: add https://cotlet.dev/mcp/v1 with the same key; the tool is peerspace_send_message. Example data.

• Respond to Peerspace booking requests before they expire
• Send a Peerspace custom offer (invite to book) from an inquiry
• Peerspace API and MCP server: every tool
• All use cases