Skip to content

Update Close.com info#4777

Merged
PeerRich merged 16 commits intomainfrom
update-close-app-description
Sep 30, 2022
Merged

Update Close.com info#4777
PeerRich merged 16 commits intomainfrom
update-close-app-description

Conversation

@joeauyeung
Copy link
Copy Markdown
Contributor

@joeauyeung joeauyeung commented Sep 30, 2022

What does this PR do?

This PR updates Close.com's app information.

https://www.loom.com/share/5134a40d3f7b43e8bf7ab6d43b3f2817

Environment: Staging(main branch) / Production

Type of change

  • Chore (refactoring code, technical debt, workflow improvements)

@vercel
Copy link
Copy Markdown

vercel Bot commented Sep 30, 2022

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated
cal ✅ Ready (Inspect) Visit Preview Sep 30, 2022 at 7:22PM (UTC)

@shirazdole
Copy link
Copy Markdown

Is is possible to say that the integration is free, but the actual service cost for that product costs x amount.

Maybe

"Cal.com Integration"
"Free"

@joeauyeung
Copy link
Copy Markdown
Contributor Author

Is is possible to say that the integration is free, but the actual service cost for that product costs x amount.

Maybe

"Cal.com Integration" "Free"

Maybe instead of just "Pricing" we should change the title to "Service Pricing" or "Provider Pricing". I can't think of the exact wording but something that conveys that Cal.com isn't the one charging for the service but the app provider is.

@leog
Copy link
Copy Markdown
Contributor

leog commented Sep 30, 2022

I'm wondering why do we need to include the service pricing information. If anyone is interested in using Close or any other paid app, they should be informed in the app official page. We just publish we have some kind of integration with that app and how we integrate, and that should be enough. Otherwise we would need to keep track of the app pricing in their official website and continuously update as they update their pricing, which seems very inconvenient.

@PeerRich
Copy link
Copy Markdown
Member

I'm wondering why do we need to include the service pricing information. If anyone is interested in using Close or any other paid app, they should be informed in the app official page. We just publish we have some kind of integration with that app and how we integrate, and that should be enough. Otherwise we would need to keep track of the app pricing in their official website and continuously update as they update their pricing, which seems very inconvenient.

agree -- we should use the price section only for our price not theirs

in this case, our close app is free

closing-- sorry @joeauyeung

@PeerRich PeerRich closed this Sep 30, 2022
@PeerRich PeerRich reopened this Sep 30, 2022
@PeerRich
Copy link
Copy Markdown
Member

lets just add this in the description

@joeauyeung joeauyeung changed the title Add price ranges to app pages and update Close.com info Update Close.com info Sep 30, 2022
@PeerRich PeerRich enabled auto-merge (squash) September 30, 2022 19:22
@PeerRich PeerRich merged commit d3f8d95 into main Sep 30, 2022
@PeerRich PeerRich deleted the update-close-app-description branch September 30, 2022 19:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants