Known Bugs & Limitations
Below is a detailed list of known bugs, limitations, and processes related to event management, text blasts, payouts, and photo uploads on Plots.
Event Tool Process
1. Changing Event URL
Users cannot manually change the event URL; this must be done on the backend.
2. Recurring Events
Recurring events are not supported at this time. Each event must be created individually.
3. Search Issue
If you encounter an issue with searching for an event or user, refer them to manual entry by an admin.
4. Analytics Limitations
Refunds and promoter payouts are not reflected in the event analytics dashboard.
Hosts must check Stripe for the most accurate earnings data.
5. Refunds Process
Refunds take up to 10 business days to process.
Refunds are completed by removing attendees from the guest list.
6. Tap-to-Pay Transactions
Users can send a receipt for tap-to-pay transactions.
However, Plots does not collect customer information for these transactions.
7. Guest List Uploads
You can upload attendees to the guest list via CSV.
Guests will receive a text message saying:
“You have been added to the guest list.”
Text Blast Process
1. Queue System
Text blasts work in a queue, meaning messages are sent in order.
Top event hosts may be assigned a priority queue for faster delivery.
99% of the time, users just need to wait for their text to send.
If there are issues beyond normal delays, escalate them to an admin.
2. Text Blast Limitations
Messages are limited to 140 characters.
No emojis or special characters (e.g., backslashes, square brackets, underscores).
The event link must fit within the character limit.
3. CSV File Uploads for Contacts
Partiful CSV – Only provides phone numbers if explicitly collected when hosting events.
Posh CSV – Allows full exports, including phone numbers.
Eventbrite CSV – Only started collecting phone numbers post-2022.
Issues uploading CSVs:
CSV files must be 3,000 contacts or fewer.
If more than 3,000 contacts, split into smaller files.
If upload issues persist, escalate to an admin.
4. Verification Process
The verification process includes Meta Pixel ID validation for certain marketing tools.
Payout Process
1. Stripe Connection & Timing
Stripe only registers revenue after it is connected.
If a user sells tickets before connecting Stripe, payouts must be manually processed by an admin.
2. Payout Schedules
Standard Payouts: Automatic 2-day rolling payments.
Manual Payouts: Available upon request.
Instant Payouts: Available for a 1% fee.
3. Stripe Account Limitations
Only the event host's Stripe account can receive payouts.
Only one payout destination is supported per event.
Photo Upload Process
1. Google Drive Requirements
Event photos must be uploaded using a Google Drive folder.
The folder must be set to "shareable" for attendees to access it.
Key things to know:
-Users get logged out every 30 days