Ürün ayrıntıları İngilizce olarak görüntülenir. Çeviriler yakında gelecek.
Kısa bilgiler
- Fiyat
- $199.00 USD
- ERPNext versiyonları
- —
- Kurulum süresi
- 30 dk.
- Lisans
- Bir kerelik kalıcı
- Diller
- 11 language
Tek Seferlik Satın Alma
Meeting Scheduler & Calendar Booking for ERPNext
Calendly-style public booking pages that sync two-way with ERPNext, Google, and Outlook calendars, then auto-create CRM activities, link Leads, and fire WhatsApp, SMS, and email reminders. Built to order by ECOSIRE for ERPNext v15/v16.
$199.00USD
Şimdi ödeme yok. Bu, ekibimize bir teklif talebi gönderir — fiyat ve sonraki adımlarla e-posta ile dönüş yapacağız.
Temel Özellikler
`Booking Page` and `Booking` DocTypes with owner, duration, pre/post buffers, min-notice, and daily booking caps configurable per page
Public availability API via `@frappe.whitelist(allow_guest=True)` methods that compute open slots from working hours minus existing `Event` records in real time
Round-robin, collective (all-hosts-free), and pooled team scheduling driven by a least-recently-assigned counter over team membership
Two-way Google Calendar sync using the Calendar API, storing the external event ID on the `Booking` for reconciliation
Two-way Microsoft 365 / Outlook sync via the Graph API, including honoring externally blocked and cancelled slots
`hooks.py` `doc_events` handler that auto-creates the linked ERPNext `Event` and a CRM activity/`ToDo` on booking submit
Automatic `Lead`/`Contact` linking via `dynamic_link` so booked meetings appear on the CRM record timeline
WhatsApp, SMS, and email reminders fired by `scheduler_events` at configurable offsets (e.g. 24h and 1h before), routed through Twilio/Meta Cloud API/your gateway
Timezone-aware slot rendering and DST-safe storage so cross-region prospects see correct local times
Reschedule and cancel self-service links backed by signed tokens, which propagate to the calendar and CRM activity
Configurable per-page intake questions written to the `Booking` and surfaced on the linked Lead
Role profiles and permission rules so hosts manage only their own booking pages while managers see the team roster
Booking confirmation and calendar `.ics` invite generated on submit for host and invitee
REST-accessible endpoints so external sites or campaign landing pages can embed availability and post bookings
Client Scripts for the public page UX (slot picker, live validation, and duplicate-submit guards)
Bu Ürün Hakkında
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.
Neden Meeting Scheduler & Calendar Booking for ERPNext
`Booking Page` and `Booking` DocTypes with owner, duration, pre/post buffers, min-notice, and daily booking caps configurable per page
Public availability API via `@frappe.whitelist(allow_guest=True)` methods that compute open slots from working hours minus existing `Event` records in real time
Round-robin, collective (all-hosts-free), and pooled team scheduling driven by a least-recently-assigned counter over team membership
Two-way Google Calendar sync using the Calendar API, storing the external event ID on the `Booking` for reconciliation
Two-way Microsoft 365 / Outlook sync via the Graph API, including honoring externally blocked and cancelled slots
`hooks.py` `doc_events` handler that auto-creates the linked ERPNext `Event` and a CRM activity/`ToDo` on booking submit
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 2 to 4 weeks 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.
Ne elde edeceksin
- Installable Frappe app source code for your ERPNext version (v15 or v16), scoped to the agreed specification
- Installation, bench setup, and configuration on your production site including calendar and reminder-gateway credentials
- Technical documentation: DocType reference, hooks, whitelisted methods, scheduler events, and sync architecture
- End-user guide plus a live training session for hosts, sales, and admins
- UAT on a staging bench with a written rollback plan before production cutover
- Post-go-live support window for bug fixes and adjustments after launch
- Git repository handover with full commit history so you own and can extend the codebase
- Written scope specification and configuration sheet (booking pages, assignment rules, sync targets, reminder offsets)
Bu kimin için
Sales team lead running inbound demos
Needs prospects to self-book qualified demo slots that distribute fairly across the pod via round-robin, land against the right Lead in ERPNext CRM, and never double-book against the rep's real calendar.
Consulting / professional services manager
Books discovery and advisory calls where the meeting must attach to a Contact and Project, honor per-consultant availability and buffers, and send reminders that cut no-shows across multiple timezones.
ERPNext administrator / systems owner
Wants a maintainable Frappe app with clean DocTypes, permission-scoped role profiles, and Google/Outlook sync that survives bench upgrades — not brittle client-side hacks or a third-party SaaS holding the calendar data.
Revenue / marketing operations
Embeds booking links in campaigns and landing pages, needs each booking to create a CRM activity and stamp attribution on the Lead, so scheduled meetings become a measurable pipeline signal.
Kuruluma genel bakış
ECOSIRE'dan indirin
Lisansı ecosire.com adresinden satın alın ve hesap kontrol panelinizden Meeting Scheduler & Calendar Booking for ERPNext uygulamasının ZIP dosyasını indirin.
Uygulamayı bankınıza ekleyin
ZIP dosyasını tezgahınızın uygulamalar klasörüne çıkarın veya çıkarılan uygulamanın yolunu içeren "bench get-app" komutunu çalıştırın.
Sitenize yükleyin
Meeting Scheduler & Calendar Booking for ERPNext yüklemek ve şemasını uygulamak için `bench --site SITE_NAME install-app APP_NAME` komutunu ve ardından `bench move'u çalıştırın.
Lisansınızı etkinleştirin
Sitenizdeki ECOSIRE Lisans ayarlarını açın ve lisans anahtarınızı etkinleştirin. Ücretsiz ecosire_connect ve ecosire_license_client uygulamalarını gerektirir.
Meeting Scheduler & Calendar Booking for ERPNext Nasıl Karşılaştırılır
| Kriter | ECOSIRE | Özel Yapı | Rakip | Odoo Yerlisi |
|---|---|---|---|---|
| Public self-booking page | Guest-accessible availability page computed from live ERPNext calendars | Buildable but you design and maintain the whole slot engine | Usually present but generic, limited availability logic | |
| Two-way Google/Outlook sync | Bidirectional via Calendar API and Graph API with reconciliation | Possible but significant integration effort per provider | Often one-way or Google-only | |
| Round-robin & team scheduling | Round-robin, collective, and pooled modes with fair assignment | Must be specified and coded from scratch | Sometimes, often behind a higher SaaS tier | |
| Auto CRM activity + Lead linking | Hooks auto-create Event, activity, and link Lead/Contact on submit | Requires custom doc_events wiring you maintain | Weak — external tool, often no ERPNext CRM link | |
| WhatsApp/SMS/email reminders | Scheduler-driven, multi-channel via your gateway | Each channel integrated and scheduled by you | Email standard; WhatsApp/SMS often paid add-on | |
| Data ownership & source access | Full app source and git repo handed over — you own it | You own it but carry all build and upkeep cost | SaaS — data and calendar live on a third party | |
| ERPNext v15/v16 fit & upgrades | Built for your version, upgrades with your bench | Depends on your team's Frappe expertise | May lag Frappe releases; compatibility not guaranteed | |
| Total cost of ownership | One-time build, no per-seat fee, optional retainer | High internal engineering and maintenance cost | Recurring per-user SaaS subscription indefinitely |
Meeting Scheduler & Calendar Booking for ERPNext hakkında Sıkça Sorulan Sorular
+How long until we can use it? This says build-to-order.
Correct — this is not an instant download. After a short scoping call we produce a written specification, then build on a staging bench, run UAT with your team, and install to production. Typical delivery is 2 to 4 weeks from confirmed scope, depending on how many sync targets and reminder channels you need.
+Which ERPNext versions do you support?
We build for ERPNext / Frappe v15 and v16. We target your exact site version so the app installs cleanly on your bench, and because you receive the source and git repo it upgrades forward with your instance.
+Does the calendar sync really go both ways?
Yes. Bookings push out to Google Calendar (Calendar API) and Microsoft 365 (Graph API) with the external event ID stored on the `Booking`, and a scheduler poll pulls external changes and blocks back in, so a slot you fill or cancel in Outlook stops showing on your public page.
+How do reminders reach clients — is WhatsApp included?
Reminders fire from a Frappe `scheduler_events` job at the offsets you set (for example 24 hours and 1 hour before). Email uses the ERPNext email queue; WhatsApp and SMS route through your gateway — Twilio, the Meta WhatsApp Cloud API, or another provider you already run. We wire it to whichever channels you confirm during scoping.
+What do we actually receive, and do we own it?
You get the full installable Frappe app source, the git repository with complete history, installation and configuration on your site, technical docs, an end-user guide, and a training session. It is your code — no per-seat SaaS fee and no vendor lock on your calendar data.
+What about support and updates after go-live?
Every build includes a post-go-live support window for bug fixes and adjustments. Beyond that we offer optional ongoing support and enhancement retainers, and because you hold the repo your own team can extend it too. We test against v15/v16 so bench upgrades are safe.
+Will this interfere with our existing ERPNext data or CRM?
No. We ship it as its own Frappe module with its own DocTypes and hook into the standard `Event`, `Lead`, and `Contact` records rather than altering them destructively. We validate everything on a staging bench with a rollback plan before touching production.
İlgili Modüller
Teklif isteyin
Meeting Scheduler & Calendar Booking for ERPNext
Calendly-style public booking pages that sync two-way with ERPNext, Google, and Outlook calendars, then auto-create CRM activities, link Leads, and fire WhatsApp, SMS, and email reminders. Built to order by ECOSIRE for ERPNext v15/v16.
- `Booking Page` and `Booking` DocTypes with owner, duration, pre/post buffers, min-notice, and daily booking caps configurable per page
- Public availability API via `@frappe.whitelist(allow_guest=True)` methods that compute open slots from working hours minus existing `Event` records in real time
- Round-robin, collective (all-hosts-free), and pooled team scheduling driven by a least-recently-assigned counter over team membership
- Two-way Google Calendar sync using the Calendar API, storing the external event ID on the `Booking` for reconciliation