-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Track contracts #307
Comments
As a starting place, we will meet with Scott, who is scoping a plan for the contract work requested by stakeholders. |
@o-ram Have we heard anything about this? I would like to see if we can get this implemented in Hubspot at some point. |
@laneymangan Add to the ODS agenda with Scott to discuss where those contracts will be stored. |
Meeting scheduled for 12/6. Contracts has been added to agenda |
Discussed with Scott, notes can be found here. To note:
|
@laneymangan unless something changes, I think we can plan to use this data for the new custom object, contracts. We will likelly work on this in Q2, so we can find sometime in May or June. I've added a |
As Cal-ITP seeks to continue collecting contracts, questions continue to arise over the role of the CS team in this effort along with contract storage. We know the following 3 items are useful for account managers: Contract vendor, products/services the contract is for, and expiration date. Contracts are currently stored in Airtable (and linked to from Hubspot) but nobody is in charge of maintaining that info or monitoring it. Questions have arisen regarding the feasibility of including greater contract info in Hubspot.
This issue serves as a placeholder for figuring out where to go next and will evolve with more specific "completion" criteria.
The text was updated successfully, but these errors were encountered: