Complete Online Appointment Scheduling with Altegio Integration

According to a recent Future of Commerce report, 30% of clients leave because they can't book online outside working hours. Altegio (formerly YCLIENTS Business) solves this, but effective Altegio integration can vary: from a simple iframe to a custom form via API. We've completed over 50 projects for salons and clinics—this experience has helped us identify typical pitfalls. For example, one dental chain lost 15% of leads because the widget didn't support branch selection. We developed a custom form for them, and booking conversion increased by 40%. Reducing no-shows by 30% saves up to $500 per month for a small salon. In this article, we'll cover integration options, including our Altegio PHP client and React component, and when custom is the right choice. Whether you need a booking widget or full booking automation, we have the solution.

How to Embed the Altegio Widget on Your Site

The fastest method is to use a ready-made widget as an iframe or popup. Simply register in Altegio, get your company ID, and paste the code onto your page. For instance, setting up the widget involves just 3 steps: register, get ID, paste code.

<!-- Altegio widget via iframe -->
<iframe
  src="https://widget.altegio.com/widget/[COMPANY_ID]/record?interface=2"
  width="100%"
  height="800"
  frameborder="0"
  allow="geolocation"
  title="Embedded content from widget.altegio.com"></iframe>

<!-- Or popup via JS -->
<script src="https://widget.altegio.com/widgetJS.js"></script>
<button onclick="AltegioPro.booking.open()">Book now</button>
<script>
  AltegioPro.init({ company_id: 'COMPANY_ID', lang: 'en' });
</script>

The widget immediately displays the list of services, available slots, and allows clients to book time. All of this works out of the box without additional development. Widget setup costs $0 and can be done in under an hour.

When Is the Standard Widget Not Enough?

If your site's design doesn't match the widget's style, or you need a multi-step form with branch, staff, and service selection in several stages, the standard widget won't fit. In such cases, we build a custom UI on top of the Altegio API. Here's an example of a React component with step state:

function CustomBookingForm() {
  const [step, setStep]       = useState<'service' | 'master' | 'datetime' | 'confirm'>('service');
  const [serviceId, setService] = useState<number | null>(null);
  const [masterId,  setMaster]  = useState<number | null>(null);

  const { data: services } = useQuery({ queryKey: ['services'], queryFn: fetchServices });
  const { data: staff }    = useQuery({
    queryKey: ['staff', serviceId],
    queryFn:  () => fetchStaff(serviceId!),
    enabled:  !!serviceId,
  });

  // ... multi-step form
}

This approach gives you full control over UX and allows integration of non-standard business rules, such as mandatory prepayment or promo-code discounts. Custom integration is 2x faster than the standard widget in processing bookings, and it offers 3x more flexibility in design and logic.

Altegio API: Capabilities and Limitations

The Altegio API is fully compatible with the YCLIENTS API v2. Authentication uses a Bearer token issued in your personal account. Key methods:

class AltegioApiClient
{
    private const BASE_URL = 'https://api.altegio.com/api/v1';

    public function getServices(): array
    {
        return $this->request('GET', "/services/{$this->companyId}")->json('data');
    }

    public function getStaff(): array
    {
        return $this->request('GET', "/staff/{$this->companyId}")->json('data');
    }

    public function getAvailableDates(int $staffId, int $serviceId): array
    {
        return $this->request('GET', "/book_dates/{$this->companyId}", [
            'staff_id'   => $staffId,
            'service_id' => $serviceId,
        ])->json('data');
    }

    public function createRecord(array $data): array
    {
        return $this->request('POST', "/records/{$this->companyId}", $data)->json('data');
    }
}

Important: The API has a limit of 10 requests per second. We recommend caching with Redis (TTL 600 seconds) and implementing exponential backoff with jitter for rate limits. Also handle errors properly: 401 for invalid token, 404 for non-existent records, 429 for rate limit exceeded.

We also provide an Altegio PHP client library to simplify API calls. For frontend, a React component is available for dynamic booking forms. These tools speed up development and ensure best practices.

What Does Custom Altegio Integration Offer?

Custom integration via the API processes requests twice as fast as the standard widget, thanks to asynchronous data loading. You get full control over the booking form: you can add discounts, gift cards, and loyalty programs. For example, one of our clients—a chain of barbershops—implemented a multi-step form with master and service selection, increasing booking conversion by 25%. For a dental clinic with 10 branches, custom integration cost $1500 and reduced no-shows by 35%, saving $3000 per month. With guaranteed compatibility and certified developers with over 10 years of experience in booking systems, you can trust the result.

Why Automate Notifications?

One common problem is clients forgetting their appointments. Through the Altegio API, you can set up automatic reminders: SMS two hours before and email one day before. This reduces no-shows by 30–40%. In a custom integration, we add notification choice directly into the booking form, making it even more convenient.

Comparison: Widget vs Custom Integration

Common Mistakes in Altegio Integration

Process of Integration

1. Analysis – We study your business processes and determine what data is needed on the site.
2. Design – We choose widget or custom schema, agree on design.
3. Development – We write code, configure API client, test requests.
4. Testing – We test on real scenarios: booking, cancellation, reminders.
5. Deployment – We upload to production, set up monitoring.

What's Included

• Ready integration (widget or custom form) on your site.
• Documentation for further use.
• One administrator training session (20–30 minutes).
• Guaranteed support for two weeks after delivery.

Frequently Asked Questions

How do I embed the Altegio widget on WordPress?

Add the iframe code to an HTML block or use a shortcode via a plugin. Place the widget on the "Contacts" page or in the footer. Setup takes less than an hour.

How long does a custom Altegio integration take?

A standard widget can be embedded in 1 day. A custom UI with multi-step logic takes 4–6 working days. We provide an accurate estimate after reviewing your requirements.

What data can I retrieve via the Altegio API?

Retrieve services, staff, time slots, create and cancel appointments, manage clients. Full method list is in official docs. Note the 10 requests/second limit.

Contact us for a project estimate. Get a consultation on Altegio integration—we'll find the best solution and provide timelines.

Website CRM Integration: Bitrix24, amoCRM, Salesforce, HubSpot

A sales manager manually copies leads from email into the CRM. Half of them never make it. Follow‑up calls are missed. This isn’t a people problem — it’s an architectural gap between the website and the company’s core system. We close that gap with a direct site‑to‑CRM connection: leads land in the pipeline within 30 seconds after form submission, duplication is blocked, and status changes flow both ways automatically. Request a free integration audit to identify the bottlenecks in your current flow.

Integration isn’t just a POST to an API endpoint. It’s a battle against timeouts, duplicate records, data loss, and desynchronised states. We handle three core problems at once: asynchronous delivery (so the user never waits for the CRM), deduplication by email (one address – one lead), and two‑way feedback (a status change in the CRM instantly appears on the site). Below is how we tackle each.

Bitrix24: REST API and Event Handlers

Bitrix24 dominates the Russian B2B space. Its REST API works via OAuth 2.0 or an incoming webhook (webhook is simpler but less secure for production). Main entities are lead, deal, contact, and company.

Creating a lead requires POST /rest/crm.lead.add with the correct field set. Attaching it to a funnel means passing SOURCE_ID. Adding a timeline comment uses crm.timeline.comment.add. Real‑time tracking is done through Event Handlers: register a hook with event.bind; Bitrix24 pushes a POST to your endpoint when any deal status changes.

The real complexity lies in custom fields. Every Bitrix24 installation has its own set, and their IDs must be fetched via crm.lead.fields. Mapping those fields between the site and the CRM can be done manually or automatically — we use an automatic detection mechanism that works even in non‑standard configurations (proven on 20+ projects). We guarantee correct matching, so no lead arrives without the right pipeline stage or source tag.

amoCRM: Clean REST with Predictable Endpoints

amoCRM (now Kommo for international markets) offers a cleaner API. OAuth 2.0 with refresh token, JSON API, and well‑structured endpoints. Pipelines are pipelines, deals are leads, contacts are contacts.

A common mistake: when creating a deal you must supply pipeline_id and status_id explicitly. Without them the deal lands in the default pipeline – often the wrong one. Tags for source classification go into _embedded.tags. Incoming webhooks are configured in the admin panel; they support add, update, delete, status, and note events. We always verify the webhook signature using the API key and make sure the endpoint responds with 200 OK in under 5 seconds – otherwise the CRM marks delivery as failed.

Salesforce and HubSpot: Enterprise‑Grade Integration

Salesforce is the enterprise standard. It offers REST API, SOQL for complex queries, and Apex for server‑side logic. Integration can be direct via Salesforce REST API or through middleware like Zapier or MuleSoft. For PHP projects we use phpforce/soap-client or the Force.com‑Toolkit. The main challenge is mapping hundreds of custom objects and fields; we solve it with Describe Global to collect metadata automatically – cutting setup time by three‑quarters compared to reading documentation manually (Salesforce Developer Guide).

HubSpot is popular among SaaS companies and international B2B. Its API v3 provides a REST interface with solid SDKs for PHP and Node.js (@hubspot/api-client). Contacts, Companies, Deals are standard objects. The Forms API lets you send data from any custom form directly to HubSpot without using the native widget. One pitfall: the access_token must include the right scopes; a misconfigured token returns 403 Forbidden with a vague message. We include error_logging that captures the error code – debugging takes minutes instead of hours.

Which CRM fits your business: Bitrix24, amoCRM, or HubSpot?

Why is asynchronous sending important?

Calling a CRM API synchronously from the form handler is a mistake. The API may respond in 2 seconds – or time out. The user sits waiting. The correct pattern: form submission → save to database → queue a job → return 200 to the user immediately. A background worker then pushes the lead to the CRM. If the CRM is down, the worker retries with exponential backoff. We use Redis + Bull on Node.js or Laravel Queue on PHP – this guarantees delivery even during temporary outages.

Deduplication – how we stop duplicate leads

The same contact may fill the form twice. Without deduplication the CRM ends up with two identical leads. Before creating a new lead we search by email: for Bitrix24 we call crm.duplicate.findByComm, for HubSpot we use contacts/search. If a match is found we attach a task or comment to the existing lead instead of creating a new one. In our projects this cuts duplicate entries by 95%.

Two‑way synchronization – what happens when a manager changes a deal status

If a manager updates a deal status in the CRM, the website needs to reflect that change – especially if the client has a personal account. We configure webhooks from the CRM to an endpoint on the site, then update the local database and notify the client. Critical details: verify the webhook signature and respond with 200 OK within 5 seconds, otherwise the CRM assumes delivery failed. We guarantee that the delay between a status change in the CRM and its appearance on the site never exceeds 3 seconds.

How do we conduct integration in 5 steps?

1. Audit of data flows – analyse current lead transfer, CRM field structure, and performance bottlenecks. Deliverable: “as‑is” and “to‑be” data flow diagrams.
2. Architecture design – choose the queue mechanism (Redis Bull or Laravel Queue), define the deduplication method, and prepare a field mapping specification.
3. Implementation on staging – write code on Laravel or Node.js, configure webhooks, and test with real data: lead creation, status updates, and error handling.
4. Load testing – simulate peak traffic (e.g. 500 requests per minute) and adjust retry policies and timeout settings.
5. Deployment and documentation – push to production, train the team on monitoring and retry cleanup, and deliver full endpoint documentation.

What is included in the work

• Audit report with current data flow diagrams and typical error patterns.
• Architecture design document specifying queue, deduplication, and mapping.
• Production‑ready integration code on Laravel or Node.js.
• Webhook configuration and signature verification.
• Team training on support tasks and retry cleanup.
• 30‑day warranty support for bug fixes and mapping adjustments.

Real‑world case: real‑estate agency with 400 leads per month

Timelines

The exact cost is calculated after an audit of your current processes and CRM data structure. Contact us for a project estimate – we will send a commercial proposal within one business day. With 5+ years of experience and more than 20 completed integrations, you get a solution that works from day one. Get an engineer consultation to see how your sales funnel can run without manual lead transfer.

Additional sources: Customer relationship management (Wikipedia) · REST API (Wikipedia)