Sales and consulting teams lose deals in the back-and-forth of "does Tuesday work for you?" — and ERPNext out of the box has no answer for it. The core Event DocType and the CRM Appointment flow can record a meeting once someone types it in, but there is no public availability page a prospect can self-book against, no round-robin distribution across a sales pod, and no live two-way sync with the Google or Outlook calendars your team actually lives in. So bookings happen in Calendly or Cal.com, the meeting never lands against the Lead, and your ERPNext CRM pipeline is missing the single most important signal: that a real conversation is scheduled.

ECOSIRE builds a proper Frappe app — its own module, not a pile of customizations — that closes this gap inside ERPNext. We add a Booking Page DocType (owner, duration, buffer times, availability windows, meeting type, assignment rule) and a Booking DocType that captures each confirmed slot. Public availability is served by whitelisted, guest-accessible methods (@frappe.whitelist(allow_guest=True)) that compute open slots from the host's working hours minus existing Event records, so a prospect books against real, current availability. On submit, a hooks.py doc_events handler on Booking creates the linked Event, writes a CRM ToDo/activity, and stamps the originating Lead or Contact via dynamic_link so the meeting shows up in the pipeline timeline automatically.

Two-way calendar sync is handled by a background integration: outbound writes push new bookings to Google Calendar (via the Calendar API / ERPNext's Google Calendar settings) and Microsoft 365 (Graph API) with the event ID stored back on the Booking; a scheduler_events cron poll reconciles external changes and cancellations so a slot blocked in Outlook stops appearing on the public page. Round-robin and team scheduling are driven by an assignment engine that reads team membership and a least-recently-assigned counter to distribute inbound meetings fairly, with collective (all-must-be-free) and pooled modes. Reminders are dispatched through your existing channels — email via the ERPNext email queue, plus WhatsApp/SMS through Twilio, Meta Cloud API, or whichever gateway you already run — fired by a scheduler event at the offsets you configure. Client scripts polish the booking page UX and timezone handling; role profiles and permission rules keep hosts scoped to their own pages while managers see the whole team.

Because this is build-to-order, nothing ships until we agree on scope. We start with a short scoping call, produce a written specification of DocTypes, assignment rules, sync targets, and reminder channels, then build on a staging bench, run UAT with your team, and install to production on your ERPNext v15 or v16 site. Typical delivery is one working week from confirmed scope. You receive the full app source and git repository — no black box, no per-seat SaaS fee, and it upgrades along with your bench.