LatePoint plugin review and common issues

Agent visibility in the booking form depends on multiple settings: (1) go to LatePoint → Agents and verify agents are published (not draft); (2) verify the agent is assigned to at least one service — agents without services do not appear in the booking flow for that service; (3) check the agent’s working hours in LatePoint → Agents → [agent] → Schedule — agents with no working hours configured show no availability; (4) if “Skip Agent Selection” is enabled in LatePoint → Settings, agents are auto-assigned and the selection step is hidden.

Go to Stripe Dashboard → Developers → Logs to see the specific API error. Common issues: (1) test mode vs. live mode mismatch in LatePoint → Settings → Payments → Stripe (test keys should only be used with Stripe test cards); (2) webhook configuration — verify the LatePoint webhook URL is registered in Stripe Dashboard → Webhooks; (3) the webhook secret must match between Stripe and LatePoint settings; (4) currency configured in LatePoint must match a currency supported by your Stripe account; (5) Stripe accounts in some countries require additional business verification before accepting payments.

Go to LatePoint → Settings → Notifications and verify email notifications are enabled for each trigger (booking created, booking confirmed, booking cancelled). Check: (1) the notification template has valid content; (2) the recipient email (customer, agent, or admin) is correctly selected; (3) WordPress email is working at all — use WP Mail SMTP’s test email to verify; (4) the notification trigger status matches the booking status that should trigger it. LatePoint bookings can be in “pending” or “approved” status — ensure notifications are configured for the status your booking workflow produces.

Go to LatePoint → Settings → Payments → General and set payment collection to “Full Payment Required” (or a deposit percentage if using the Deposit add-on). When payment is required, the booking form adds a payment step before the confirmation screen — clients must complete payment for the booking to be confirmed. Unpaid bookings remain in “pending” status. Configure the booking status flow in LatePoint → Settings → Statuses to determine whether unpaid bookings are automatically cancelled after a time period.

LatePoint provides a shortcode [latepoint_book_button] for placing a “Book Now” button that opens the booking overlay, or [latepoint_form] to embed the booking form inline on a page. For Gutenberg, the LatePoint Gutenberg block is available in the block inserter. The inline form shortcode accepts parameters to pre-select specific services, agents, or locations: [latepoint_form service_id=”1″ agent_id=”2″] — this pre-fills the booking form to skip those selection steps.

Both are top choices for salons where booking UX quality matters. LatePoint has a more distinctive animated interface that many describe as more impressive on first impression. Amelia has a more comprehensive feature set (particularly for multi-location and group events/classes) and an all-inclusive pricing model without needing to purchase add-ons separately for SMS. For a boutique salon prioritizing booking form aesthetics, LatePoint’s visual design may edge ahead. For a busier salon needing robust staff management and built-in SMS reminders, Amelia’s comprehensive feature set at a predictable price is often the practical choice.

LatePoint supports setting a capacity (maximum attendees) for services, enabling group or class-style bookings where multiple clients can book the same time slot until the capacity is reached. For more structured class management with session schedules and class-specific registration pages, the Amelia Events feature or a dedicated class booking plugin provides more granular class management. LatePoint’s capacity feature handles the core case of multi-attendee appointments.

Yes, that can happen, especially on older sites with many plugins. This usually happens when the plugin, theme, and add-ons are updated out of sequence. In most cases, testing on staging catches the issue before it reaches the live site. From experience, backups and changelog reviews save a lot of cleanup time.

Start by checking whether another plugin already does the same job. In most cases, overlap is what creates avoidable conflicts and performance issues. A common issue is installing a plugin because it looks convenient without checking the stack first. From experience, a short compatibility review avoids most of the pain later.