DIRECT ANSWER
Use a link when the visitor simply needs to reach another tool. Consider an embed when an approved external interface should appear inside your page. Scope an integration when systems must exchange or synchronize data. Confirm the provider's actual capabilities before promising any of these behaviors.
Describe the customer action first
“Add booking” is incomplete. It could mean opening an existing booking page, placing that booking interface on the website or building a workflow that exchanges appointment data with another system.
Write down what the visitor does, where the authoritative record lives and what the website must know afterward. Those answers define the work more precisely than a logo on a proposal.
Integrations are one of the five factors in what makes a website project complex. For an illustrative example of ordering, catering and event connections inside one business, see how a neighborhood cafe can grow.
Distinguish the connection types
| Approach | What it does | What must be verified |
|---|---|---|
| Link | Opens the destination | Correct destination, access and clear visitor expectations |
| Embed | Displays supported external content within the page | Provider permission/support, mobile behavior and fallback |
| Integration | Exchanges data through a defined mechanism | Available interface, authorization, data mapping and failure handling |
MDN explains that an iframe embeds another HTML page within the current one. A visible embedded screen does not, by itself, establish that the surrounding website receives the screen's business data.
Link, embed or integration?
If data must move between systems, scope an integration. If not, and the outside interface must appear on your page, verify a supported embed. Otherwise use a clear link.
Ask what stays in sync
For data exchange, identify the source of truth for each field. State whether updates move one way or both ways, what triggers them and what delay is acceptable. Describe what happens when a record is changed in both places or a connection fails.
These are scoping requirements. They are not promises that a specific vendor supports a given workflow.
Browser access to another origin is subject to technical controls. MDN's CORS documentation explains how servers specify which origins can access resources through browser requests. Do not assume that a public web page is an unrestricted data interface.
Include the failure path in the scope
A useful brief names what the customer sees if the external system is unavailable. It also identifies who receives an operational alert and how a missing or duplicate record is resolved, where those behaviors are required.
If the website only needs to send the visitor to an existing tool, a well-labeled link may meet the requirement. If confirmed synchronization is essential, an attractive embed alone is insufficient evidence of completion.
Keep the commercial boundary clear
At SIS, Growth is intended for a complete business website that works with existing tools through approved links or embeds. Authority can include deeper, explicitly scoped integrations alongside the Knowledge Catalog and strategy work. Neither package name guarantees a vendor's access, subscription rights or technical capability.
Define the needed behavior before selecting scope. Use the proposal comparison guide to identify third-party fees and continuing responsibilities without assuming they are included.
For an inquiry system, check the full form-delivery path. For interactive decision tools, compare assessments, forms and calculators.
Describe the existing tool and the behavior you need. Keep account passwords and private customer records out of the brief.
Sources and method
MDN supports the iframe and cross-origin explanations. The decision table and integration questions are SIS scope recommendations. SIS package boundaries follow the approved October 10, 2026 implementation brief; no live integration capability is claimed.
Sources verified October 10, 2026: