chore: update CTA from book a call to get in touch, add .gitignore

[MantisClone]

Problem

The current CTAs across documentation use "Book a Call" with Calendly links, which needs to be updated to a unified "Get in Touch" messaging with HubSpot form URLs.

Proposed Solution

• Updated all 8 documentation pages to use "Reach out" / "get in touch" CTA messaging
• Replaced Calendly booking links with HubSpot form URL including UTM tracking parameters

Secondary Changes

• Added .gitignore file with .ignore/ pattern to exclude local development files

Fixes RequestNetwork/public-issues#67

[coderabbitai]

Walkthrough

Eight documentation pages updated to replace CTA copy from "Book a Call" / "Talk to an expert" to "Get in touch" / "Reach out" and swap Calendly booking links for HubSpot form URLs; also added a new .gitignore rule for a .ignore/ directory.

Changes

Cohort / File(s)	Summary
Root docs docs/README.md	Replaced hint "Talk to an expert" → "Reach out" and updated booking link to HubSpot "get in touch" URL.
Request Network API — general CTAs docs/request-network-api/batch-payments.md, docs/request-network-api/create-and-pay-requests.md, docs/request-network-api/crosschain-payments.md, docs/request-network-api/easyinvoice-api-demo-app.md, docs/request-network-api/recurring-payments.md, docs/request-network-api/supported-chains-and-currencies.md	Replaced "Talk to an expert" → "Reach out"; updated CTA wording to "get in touch" and replaced Calendly URLs with HubSpot form links (product-specific UTM content).
Request Network API — crypto-to-fiat docs/request-network-api/crypto-to-fiat-payments.md	Updated "Production Access - Launch When Ready" CTA from "Book a call" to "Get in touch" with HubSpot form URL.
Repo config .gitignore	Added ignore rule for .ignore/ directory.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Out of Scope Changes check	⚠️ Warning	An unrelated change to .gitignore was introduced (adding '.ignore/' rule) that is not mentioned in the linked issue objectives, making it an out-of-scope addition.	Remove the .gitignore modification as it is unrelated to the CTA update objective in issue #67; include it in a separate PR if necessary.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Linked Issues check	✅ Passed	The PR addresses the linked issue #67 by replacing 'Book a Call' CTAs with 'Get in touch' across 8 documentation pages using the HubSpot form URL with correct UTM parameters.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main changes: updating CTAs from 'book a call' to 'get in touch' and adding .gitignore, which aligns with the primary content changes across multiple documentation files.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[greptile-apps]

Greptile Overview

Greptile Summary

This PR updates the call-to-action (CTA) language across 8 documentation files, changing from "book a call" with Calendly links to "get in touch" with a HubSpot form that includes UTM tracking parameters.

Changes Made

• Header: Changed from "Talk to an expert" to "Reach out"
• Body text: Updated to "For more details on how to start accepting crypto payments, get in touch and we will reach out."
• URL: Replaced Calendly links with HubSpot form URL including UTM parameters (utm_source=request.network&utm_medium=docs&utm_campaign=evergreen&utm_content=get_in_touch)

Files Updated

All 8 target files have been successfully updated with the new CTA:

• Main documentation page (README.md)
• 7 API documentation pages (batch-payments, create-and-pay-requests, crosschain-payments, crypto-to-fiat-payments, easyinvoice-api-demo-app, recurring-payments, supported-chains-and-currencies)

Consistency Note

The PR description states all CTAs have been updated, but there's one remaining old Calendly link in batch-payments.md line 37 (linking to a different person: mariana-rn). Additionally, migrate-to-v2.md was not included in this update and still contains an old Calendly link. Consider whether these should also be updated for complete consistency across all documentation.

Confidence Score: 5/5

• Safe to merge - this is a straightforward documentation update with no code changes
• This PR only updates documentation text and URLs. The changes are simple string replacements that cannot break existing functionality. All updated files follow a consistent pattern with the same CTA message and properly formatted HubSpot URL with UTM parameters. The only issue is an inconsistency where one additional Calendly link was not updated, but this is a minor style/consistency concern rather than a blocking issue.
• docs/request-network-api/batch-payments.md contains one remaining old Calendly link that may need updating for consistency

Important Files Changed

File Analysis

Filename	Score	Overview
docs/README.md	5/5	Updated CTA header and link from Calendly to HubSpot form with UTM tracking
docs/request-network-api/batch-payments.md	3/5	Updated CTA at top, but line 37 still contains old Calendly link (different person)
docs/request-network-api/create-and-pay-requests.md	5/5	Updated CTA header and link from Calendly to HubSpot form with UTM tracking
docs/request-network-api/crosschain-payments.md	5/5	Updated CTA header and link from Calendly to HubSpot form with UTM tracking
docs/request-network-api/crypto-to-fiat-payments.md	5/5	Updated inline "Book a call" link to "Get in touch" with HubSpot form URL
docs/request-network-api/easyinvoice-api-demo-app.md	5/5	Updated CTA header and link from Calendly to HubSpot form with UTM tracking
docs/request-network-api/recurring-payments.md	5/5	Updated CTA header and link from Calendly to HubSpot form with UTM tracking
docs/request-network-api/supported-chains-and-currencies.md	5/5	Updated CTA header and link from Calendly to HubSpot form with UTM tracking

Sequence Diagram

sequenceDiagram
    participant Author
    participant Docs
    participant Marketing
    
    Marketing->>Author: Request CTA update to "get in touch"
    Author->>Docs: Update 8 files with new HubSpot form URL
    Author->>Docs: Change header to "Reach out"
    Author->>Docs: Update CTA text with UTM parameters
    Docs-->>Marketing: New CTAs with tracking enabled

Loading

[greptile-apps]

_{1 file reviewed, 1 comment}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

Additional Comments (1)

docs/request-network-api/batch-payments.md
[P2] This line still contains an old Calendly link ("Book a call") that should be updated to match the new "get in touch" CTA strategy. Update this to use the new HubSpot form URL with UTM parameters for consistency across all documentation.

Prompt To Fix With AI

This is a comment left during a code review.
Path: docs/request-network-api/batch-payments.md
Line: 37:37

Comment:
[P2] This line still contains an old Calendly link ("Book a call") that should be updated to match the new "get in touch" CTA strategy. Update this to use the new HubSpot form URL with UTM parameters for consistency across all documentation.

How can I resolve this? If you propose a fix, please make it concise.

[coderabbitai]

Actionable comments posted: 0

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

docs/request-network-api/batch-payments.md (1)

37-37: Missed CTA update - blocking inconsistency.

Line 37 still contains the old "Book a call" CTA with a Calendly link. This contradicts the PR objective to replace all such CTAs with the standardized "get in touch" messaging and HubSpot form URL.

📜 Review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c6a93ce and cc804aa.

📒 Files selected for processing (8)

• docs/README.md
• docs/request-network-api/batch-payments.md
• docs/request-network-api/create-and-pay-requests.md
• docs/request-network-api/crosschain-payments.md
• docs/request-network-api/crypto-to-fiat-payments.md
• docs/request-network-api/easyinvoice-api-demo-app.md
• docs/request-network-api/recurring-payments.md
• docs/request-network-api/supported-chains-and-currencies.md

🧰 Additional context used

📓 Path-based instructions (1)

**/*

⚙️ CodeRabbit configuration file

**/*: - Only comment on issues that would block merging — ignore minor or stylistic concerns.

• Restrict feedback to errors, security risks, or functionality-breaking problems.
• Do not post comments on code style, formatting, or non-critical improvements.
• Keep reviews short: flag only issues that make the PR unsafe to merge.
• Limit review comments to 3–5 items maximum, unless additional blockers exist.
• Group similar issues into a single comment instead of posting multiple notes.
• Skip repetition — if a pattern repeats, mention it once at a summary level only.
• Do not add general suggestions; focus strictly on merge-blocking concerns.
• If there are no critical problems, respond with minimal approval (e.g., 'Looks good'). Do not add additional review.
• Avoid line-by-line commentary unless it highlights a critical bug or security hole.
• Highlight only issues that could cause runtime errors, data loss, or severe maintainability issues.
• Ignore minor optimization opportunities — focus solely on correctness and safety.
• Provide a top-level summary of critical blockers rather than detailed per-line notes.
• Comment only when the issue must be resolved before merge — otherwise, remain silent.
• When in doubt, err on the side of fewer comments — brevity and blocking issues only.
• Avoid posting any refactoring issues

Files:

• docs/request-network-api/easyinvoice-api-demo-app.md
• docs/request-network-api/crosschain-payments.md
• docs/README.md
• docs/request-network-api/create-and-pay-requests.md
• docs/request-network-api/crypto-to-fiat-payments.md
• docs/request-network-api/recurring-payments.md
• docs/request-network-api/supported-chains-and-currencies.md
• docs/request-network-api/batch-payments.md